List builds

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds no extra behavioral context such as pagination, response format, or scope limitations beyond what is implied by 'for an app'.

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, efficient sentence that front-loads the core purpose. Every word earns its place with no redundancy.

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?

With 7 parameters and a minimal description, the text only hints at the version filter, omitting the required app filter and other available filters. While the detailed schema compensates, the description alone is somewhat incomplete and could mislead an agent into thinking version is the only optional filter.

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 input schema covers all parameters with 100% coverage, so the description does not need to explain them. It adds one note about 'optionally filter by version' but that is redundant with the schema and does not provide additional meaning for other filters like processingState or preReleaseVersion.

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 tool 'List builds for an app', with a specific verb and resource. It distinguishes from the singular 'get-build' sibling by indicating multiple builds. However, 'for an app' is singular while the filter.app parameter accepts an array, and only the version filter is mentioned, which slightly narrows the scope.

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?

Usage context is implied by the verb 'List' but no explicit guidance is given about when to use this tool versus alternatives like 'get-build' or 'list-build-beta-details'. No exclusions or preconditions are stated.

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