Get App Store app profile

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable behavioral context: page-sourced fields are best-effort, include_page_data triggers an extra request, and include_raw returns a large payload to be used sparingly. No contradiction with annotations.

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 four sentences, front-loaded with the main action, and every sentence adds value. No redundant or unnecessary words.

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?

Given the presence of a thorough input schema, output schema, and annotations covering read-only and idempotent behavior, the description covers the main purpose and optional behaviors well. It could mention when to prefer sibling tools, but overall it provides sufficient context for an agent to use the tool correctly.

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 coverage is 100% and descriptions are already good, but the description adds extra nuance: app_id_or_url can be numeric or URL, country defaults to URL's country or 'us', include_raw is 'large - only when normalized fields are not enough', and include_page_data is 'best-effort, one extra request'. This enhances understanding beyond schema alone.

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 explicitly states 'Fetch the full public App Store profile for one app by numeric ID or apps.apple.com URL', using a specific verb and resource. It clearly differentiates from sibling tools like search_app_store, get_app_store_reviews, etc., by focusing on a single app's profile.

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 provides clear guidance on when to use the tool (for one app by ID or URL) and explains optional parameters (include_page_data, include_raw) with their trade-offs. However, it does not explicitly contrast with sibling tools or state when not to use this tool, e.g., when to use search instead.

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