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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral fact—the data comes from Apple's public iTunes API (external, open-world source)—but says nothing about rate limits, pagination, authentication, or the cut-off 'AI' capability it teases.

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 is literally repeated verbatim, then cut off mid-clause twice ('rating…', '— with an AI…'). This is garbled output rather than efficient writing, and the meaningful content is not front-loaded cleanly.

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 tool with an opaque nested 'input' object and no output schema, the description should explain what inputs are accepted and what the 'AI' layer returns. Instead it is truncated, leaving the return shape and the AI functionality entirely unexplained.

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 100%, so the single 'input' object parameter is technically documented. The description adds no usable parameter semantics (no term formats, ID vs. name conventions) beyond restating the lookup intent, so the baseline 3 applies.

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 phrasing 'Look up any iOS app or developer via Apple's public iTunes API' conveys a specific verb and resource, and the metadata list (ratings, category, price, version history) sharpens it. However, the sentence is duplicated and truncated ('rating…', '— with an AI…'), so the intended scope is never fully stated and it does not distinguish itself from app-adjacent siblings like app_review_intelligence or aso_insights.

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?

There is no when-to-use guidance, no exclusions, and no named alternative anywhere in the text. An agent cannot tell from this description when to pick this over app_review_intelligence, aso_insights, or greenlit.

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