get_builder_report_summary

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

With no annotations, the description carries the full burden. It explicitly states 'Read-only' and lists systems not modified (repository files, git state, release state, configuration), providing valuable safety assurances beyond the tool's name.

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 concise with two clear sentences. It efficiently communicates the tool's nature and safety profile, though it could be improved by briefly noting parameter dependencies 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?

The description is incomplete given the context: five optional parameters with no guidance, no output schema, and 0% schema coverage. It does not explain how to specify a report or what the summary contains, leaving the agent with insufficient information to use the tool correctly.

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 description coverage is 0%, and the description provides no information about the five parameters (maxChars, reportPath, workCardId, phaseFolder, workspaceId). The agent cannot infer which parameters are needed or how they affect the result.

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 returns a 'bounded Builder Report preview' from a 'safe report lookup', identifying the resource and action. However, it does not explain what a Builder Report is or what the preview contains, leaving some ambiguity.

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 implies usage for retrieving a report summary without modification, but lacks explicit guidance on when to use this tool over siblings like get_builder_report_index or get_change_set_readiness_summary.

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