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 burden is lower. It adds value by specifying the default sort order ('newest first with sort=-uploadedDate'), summarizing filtering options, and indicating the HTTP method. It does not contradict annotations.

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 extremely concise: two sentences front-load the purpose and key behavior (cross-app, default sort, filters), then provides the alternative usage. 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?

Given the tool has 19 parameters and no output schema, the description is somewhat minimal. It lacks guidance on important usage patterns like pagination (next_url), relationship inclusion (include parameter to save API calls), and the fact that the response is a paginated list. While schema descriptions cover individual parameters, the overall context for an LLM to use the tool efficiently is incomplete.

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 baseline is 3. The description mentions 'Filter by app, version or processing state,' which summarizes some filters but does not add meaning beyond the schema's parameter descriptions. No novel semantic information is provided.

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 explicitly states what the tool does: 'List uploaded builds across all apps, newest first with sort=-uploadedDate.' It clearly identifies the resource (builds) and the action (list), and distinguishes itself from the sibling tool apps__builds__list by specifying cross-app 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?

The description provides explicit guidance on when to use this tool versus the alternative: 'For one app's builds use apps__builds__list instead.' This directly tells the agent which tool to select based on the query scope, fulfilling the highest standard for this dimension.

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