Search iOS apps

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

Annotations already provide safety info (readOnly, idempotent, non-destructive). Description adds no behavioral traits beyond the stated filters; e.g., no mention of pagination, sorting defaults, or rate limits.

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?

Single sentence, 16 words, no filler. Front-loaded with verb and resource. Efficiently conveys core purpose.

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?

Despite 11 parameters and no output schema, description omits crucial context like result format, pagination behavior, and sorting details. Schema coverage is low, leaving many parameters undocumented.

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 only 36%, but description lists only high-level filter dimensions (keyword, category, rating, etc.) without detailing specific parameters or constraints. Many parameters (offset, sort_by, sort_dir, min_*) are not addressed, insufficiently compensating for low coverage.

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?

Description clearly states verb (search and filter) and resource (iOS App Store apps) and lists many filter dimensions. Distinguishes well from siblings like get_app_detail and get_app_reviews.

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?

Implied usage for searching/filtering, but no explicit guidance on when to use this tool vs. siblings like get_app_detail or get_app_reviews. No when-not or alternative advice.

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