reject_override

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

With no annotations, the description carries the full behavioral burden. 'Record' implies a write/mutation, but the description does not disclose whether the rejection finalizes the approval, whether it is reversible, whether it sends notifications, or what side effects occur in the surrounding process.

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 short sentence with no filler or repetition. It front-loads the core purpose, though the word 'explicit' adds only marginal value and could be dropped without losing meaning.

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 no annotations, no parameter documentation, and no usage context, the description is too thin for reliable invocation. An agent does not know the intended place in the approval lifecycle, what the output schema will return, or how rejection differs operationally from approval besides the obvious polarity.

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 must compensate, but it adds no parameter-level meaning. 'approval_id' and 'decided_by' are loosely inferable from 'rejection decision', but 'decision_ref' remains unexplained, and no parameter formats, purposes, or relations to the workflow are given.

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 states a clear action ('Record') and object ('an explicit rejection decision'), so an agent understands the tool logs/commits a rejection. It distinguishes from siblings like approve_override and request_override by naming rejection explicitly, though it could be more precise by saying it rejects an override approval.

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 about when to use this tool versus approve_override, request_override, or list_approvals. The description does not state prerequisites, sequencing in the approval workflow, or situations where this tool should not be used.

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