apps__builds__list

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's addition of the endpoint URL and ordering is moderate. It does not disclose potential pitfalls like pagination behavior or response size limits, but annotations suffice for safety.

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 concise (one sentence plus endpoint) with no wasted words. It could benefit from clearer separation of elements, but it efficiently communicates the 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?

Given the simple tool type (list with pagination) and rich annotations, the description covers essentials: scope, ordering, and endpoint. It does not describe return values (no output schema), but that is acceptable.

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%, so the description is not required to add parameter details. It does not provide additional meaning beyond the schema, justifying baseline 3.

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') and resource ('builds uploaded for an app'), specifies default sorting order ('newest first when sorted by -uploadedDate'), and includes the endpoint URL. It effectively distinguishes from the sibling 'builds__list' by scoping to a specific app.

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 context for when to use this tool (listing builds for a specific app) and implies ordering behavior. However, it lacks explicit guidance on when not to use it or alternatives, such as the sibling 'builds__list' for cross-app queries.

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