list_app_versions

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it retrieves a list, but does not mention read-only nature, potential side effects, sorting, filtering limits, or error handling. The description is minimal and lacks crucial context for safe invocation.

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 short sentence, front-loading the core purpose. However, it is perhaps too concise given the lack of annotations and parameter details; a slightly more informative description would maintain conciseness while improving clarity.

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 low complexity (2 parameters, no nested objects, no output schema), the description is incomplete. It does not mention that appId is required, that limit is optional with a maximum of 50, or what the output looks like. The description fails to provide sufficient context for correct usage.

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 50% (appId has a description, limit does not). The description does not explain the parameters at all, leaving the agent to rely solely on the schema. It fails to add meaning beyond what the schema provides, especially for the limit parameter which has no description in schema.

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 action ('get a list') and the resource ('App Store versions of an app'), distinguishing it from sibling tools like list_apps (which lists apps) and get_app_info (which retrieves a single app). The verb and resource are specific and unambiguous.

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 no guidance on when to use this tool versus alternatives, such as get_app_info for a single version or list_apps for app-level data. No prerequisites or exclusions are mentioned.

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