reject_change

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

With no annotations provided, the description carries full burden but offers no behavioral disclosure. It doesn't state whether this is a destructive/mutative action, what permissions are required, how it affects the change request lifecycle, or what the expected outcome is. For a tool that likely alters system state, this lack of transparency is critical.

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, straightforward sentence with no wasted words. It's front-loaded with the core action and resource. While under-specified, it achieves maximum conciseness for its limited 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?

Given the tool's likely complexity (state-changing operation in a change management context), no annotations, no output schema, and poor parameter documentation, the description is severely incomplete. It doesn't explain the tool's role in workflows, error conditions, or system impact, making it inadequate for safe and effective use.

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 mentions no parameters, while the schema has 3 parameters (change_id, rejection_reason, approver_id) with 0% schema description coverage. The schema provides basic titles but no contextual meaning. The description fails to compensate by explaining what these parameters represent or how they're used, leaving semantics largely undocumented.

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 'Reject a change request' restates the tool name 'reject_change' almost verbatim, making it tautological. It specifies the verb 'reject' and resource 'change request', but lacks any detail about what rejecting entails or how it differs from alternatives like 'approve_change'. This provides minimal value beyond the name itself.

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 guidance is provided on when to use this tool versus alternatives. The sibling list includes 'approve_change', but the description doesn't mention it or explain the decision context (e.g., after review, based on criteria). There's no indication of prerequisites, sequencing, or exclusion conditions, leaving the agent with no usage context.

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