list_caches

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

The description indicates a read-only operation ('List'), which aligns with the name. However, with no annotations provided, the description does not disclose any behavioral traits such as rate limits, pagination, or safety. It relies solely on the word 'List', which is minimal.

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 very short (one line plus parameter list), which is appropriate for a simple one-parameter tool. It is front-loaded with the purpose. However, it could afford to add a bit more detail without becoming verbose.

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 simplicity of the tool (one required parameter, no output schema), the description is adequate but not fully complete. It lacks details about what the returned list contains (e.g., cache names, sizes) and whether there is any pagination or filtering.

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 Codemagic application ID', which adds slight clarification. However, the schema already has a title 'App Id', and the coverage is 0% in the schema description. The description does not provide additional format, constraints, or examples.

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 ('List all build caches') and the resource ('for a Codemagic application'). It is specific to listing caches, but does not explicitly differentiate from sibling tools like 'delete_cache' or 'delete_all_caches'.

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 such as 'delete_cache' or 'delete_all_caches'. There is no mention of prerequisites, context, or recommended scenarios.

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