query_changes

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

With no annotations, the description carries the full burden of behavior disclosure, but only states 'searches'. It does not describe the return format, the effect of 'limit' or 'options', how 'gerrit_base_url' is used, or any other behavioral details that would help the agent anticipate side effects or output.

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 sentence, front-loaded with the core action. It contains no filler or redundancy, making it highly concise and easy to parse.

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 severely under-specified for a tool with 4 parameters, no annotations, and no output schema. It lacks essential context such as query syntax, result limits, configuration options, and how it relates to sibling tools, making it inadequate for reliable tool selection and invocation.

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 description only hints at the 'query' parameter ('query string') and completely ignores 'limit', 'options', and 'gerrit_base_url'. Since schema description coverage is 0%, the description fails to compensate for the missing parameter explanations, leaving most parameters underspecified.

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's function: searching for CLs (change lists) based on a query string. It uses a specific verb and resource, and implies a free-form query input, which differentiates it from the more structured sibling query_changes_by_date_and_filters, though not explicitly.

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 indicate when to use this tool versus alternatives such as query_changes_by_date_and_filters or get_change_details. There is no mention of prerequisites, contexts, or when not to use it.

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