get_app_caches

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

The description implies a read operation ('Retrieve') but does not explicitly state it is non-destructive or discuss permissions, rate limits, or error conditions. With no annotations, this is insufficient.

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 short and uses a clear 'Args/Returns' format. It is front-loaded but could be more informative without adding length.

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?

While the output schema exists to describe return values, the description lacks usage context and behavioral details. It is adequate for a simple list tool but missing sibling differentiation and edge cases.

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 parameter 'app_id' is described as 'The application identifier', which adds minimal meaning beyond the schema's 'App Id' label. No format, constraints, or examples are provided, leaving gaps for a required parameter.

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 it retrieves a list of caches for an application, with a specific verb and resource. It differentiates from sibling delete operations, though not explicitly.

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?

No guidance is provided on when to use this tool versus alternatives like delete_app_cache or delete_all_app_caches. It does not mention use cases or prerequisites.

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