getOperationsForApp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only says 'recent operations' but does not explain what 'recent' means, whether there are pagination limits, ordering, or permission requirements. The tool appears to be a read-only getter, but this is not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one concise, clear sentence with no fluff. It is appropriately sized for a simple getter tool, though it could include a bit more detail without becoming verbose. The structure is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While an output schema exists (so return values are documented), the description lacks essential context: it does not explain the optional account_handle parameter, provide usage guidance relative to sibling tools, or disclose any behavioral constraints. This makes the description incomplete for confident tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not compensate. It implies 'app_handle' identifies the app, but the optional 'account_handle' parameter is completely unexplained. The description adds little meaning beyond what the parameter names suggest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb+resource: 'Get recent operations for a specific app.' It specifies the scope ('for a specific app') which distinguishes it from siblings like getOperationsForDatabase and getOperationsForVhost, but it does not explicitly differentiate from getOperationLogs, which could overlap. Still, the core purpose is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like getOperationLogs or getOperationsForDatabase. The description only states what it does, not the context or exclusions. No when-to-use or when-not-to-use information is present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.