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

The description discloses important behavioral traits beyond the annotations: evidence text remains unverified, no approval or source revision is changed, and the operation is tied to the exact revision the agent read. It also states permission requirements. It could additionally clarify whether this creates a new request or updates an existing one, but overall it meaningfully expands on the annotations.

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?

Three concise sentences, with the core action and revision constraint front-loaded and boundary conditions stated immediately after. Every sentence earns its place; there is no filler or repetition of schema content.

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 covers the core behavioral contract and prerequisites, but with no output schema it does not explain what the tool returns or how to confirm the request was recorded. It also leaves ambiguous what happens with previously recorded change requests and how downstream approval would connect. These are important gaps for a mutation tool with a nested originalRevision object.

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 only 43%, so the description should compensate. It does add some value by indicating that the operation targets one row and must reference the exact revision read, and by telling the agent that evidence text will not be verified. However, it does little to clarify notes, sourceTitle, or rowId beyond what the schema already offers.

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 names a specific action ('Record a request for changes'), a specific resource ('one matrix row'), and a critical timing constraint ('at the exact analysis revision you read'). It clearly differentiates this from generic review/request siblings by noting that it does not change approvals or source revisions.

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 gives clear context for when this tool is appropriate: when the agent holds review scope and a reviewer role and wants to record requested matrix changes. It does not explicitly name alternative tools or state when NOT to use this tool, but its prerequisites and scope are concrete enough to guide selection.

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