get_change_details

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

Without annotations, the description carries full responsibility for behavioral disclosure. It merely says 'Retrieves', implying a read operation, but gives no details about return format, pagination, permissions, or what 'comprehensive summary' includes. No side effects, rate limits, or output behavior are disclosed.

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 compact and front-loaded with the action verb, but it is under-specified. While no words are wasted, the single sentence fails to provide enough substance to be considered effective conciseness; it is merely terse.

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 3 parameters, no output schema, and no annotations, the description is inadequate. It does not explain what 'comprehensive summary' contains, how options or gerrit_base_url influence the result, or what the return value looks like.

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 has 3 parameters with 0% description coverage, and the description adds no meaning beyond the parameter names. 'options' is particularly vague, and there is no explanation of what data each parameter expects or how it affects the retrieval.

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 uses a specific verb ('Retrieves') with a distinct resource ('comprehensive summary of a single CL'), clearly distinguishing it from sibling tools that fetch individual components like commit messages or file lists. The scope ('single CL') differentiates it from query_changes.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives, nor does it mention any prerequisites, exclusions, or situations where a different tool would be preferable.

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