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

With no annotations provided, the description carries the burden and discloses the key trait: 'Nothing is applied automatically — a person reviews and merges,' preventing the agent from assuming an auto-merge. It also mandates running and reporting tests. It does not mention permissions or what failure looks like, so it falls short of a 5.

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?

Front-loads the purpose before the branching usage, behavior, and precondition. It is dense but every sentence carries information; only minor tightening is possible.

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?

For a 7-parameter mutation with no annotations or output schema, the description covers purpose, usage branching, human-review behavior, and test reporting. It omits return-value expectations (e.g., a PR link) and the role of 'page', leaving small gaps 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 coverage is 71%, and the description adds real meaning beyond the schema by clarifying the either/or relationship between feedback_id and text, which is not encoded in the schema. It also ties 'tests' to the reporting precondition, though the 'page' parameter is left unexplained in both places.

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?

States a specific verb and resource: open a pull request carrying a unified diff against the Team Meet source for a fix request. This clearly distinguishes it from siblings like send_feedback (reporting) and send_message (chat), so an agent can select it without opening the schema.

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?

Explicitly branches usage: give feedback_id to attach to an existing request (naming send_feedback and GET /api/fixes as sources for open requests), or give text to file the request and attach the fix in one step. It also states a precondition (run the touched tests first). Conditions and alternatives are both spelled out.

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