query

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

With no annotations and no description, there is zero disclosure of behavioral traits. An agent cannot tell whether this is read-only, mutating, network-bound, or what side effects it might have. The description provides no value 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 extremely short, but this is under-specification rather than conciseness. It front-loads nothing useful; a single word provides no information.

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 13 parameters, 5 required, and no output schema or annotations, the description is drastically incomplete. An agent has no idea what the tool returns, what inputs are needed beyond their names, or what edge cases exist. This is entirely inadequate for a tool of this complexity.

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%, so the description carries the full burden of explaining the 13 parameters, but it explains nothing. Required parameters like 'query', 'repository_id', and 'snapshot_id' have no semantic meaning added beyond their names.

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?

Tautological: description restates name/title.

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?

There is no guidance whatsoever about when to use this tool versus the dozens of alternatives in the sibling list. The description contains no context, conditions, or exclusions.

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