app_store_review_attachments__get

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description aligns with these. The description adds no additional behavioral context such as pagination, error handling, or rate limits, beyond restating that it's a read operation. With annotations present, this is adequate but not enriched.

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 a single sentence that front-loads the action ('Read'), includes the resource and ID scope, and even embeds the endpoint path. Every element adds value, with no waste or redundancy.

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?

For a simple get-by-ID tool with annotations covering safety and schema covering parameters, the description plus structured fields are sufficient. It does not explain return values, but with no output schema, this is not a critical gap for such a standard read operation. The endpoint path adds useful API context.

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?

The input schema provides 100% coverage of all three parameters, each with a clear description (e.g., 'id' explains it comes from a matching list call). The description itself adds no parameter-level meaning, so baseline 3 is appropriate.

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 uses a specific verb ('Read') with a specific resource ('App Store review attachment') and scoping ('by ID'). The endpoint path is also included, making the operation unmistakable. It clearly distinguishes from create/update/delete and from the list operation.

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?

The description clearly indicates this is for reading a single attachment when you have its ID, providing clear context for use. However, it does not explicitly mention when not to use it or recommend an alternative (e.g., the list endpoint), so it falls short of explicit exclusion guidance.

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