approvals_reject_work_item

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the REST path, which merely restates the annotation title: no word on resulting state transitions, whether the rejection is reversible, whether a reason/formEntries payload is mandatory, or what permissions are required.

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?

Two short lines with the action front-loaded. The second line is a raw POST path that duplicates the annotation title and earns little space, but the definition is not bloated.

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 non-idempotent mutation in an approval workflow with a nested request body and no output schema, the description omits the essentials: what rejection does to the work item/approval request, whether the body is required content, and what the caller gets back. An agent could invoke it but not predict its effects.

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 nominally 100%, so the baseline is 3, but the schema descriptions are vacuous ('(path)' and 'Request body') and the nested formEntries object is entirely unexplained. The description does nothing to clarify that the body carries rejection form data, so it neither helps nor hurts relative to the schema.

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 ('Rejects the specified work item'), which is more informative than the name alone. However, it does not differentiate itself from siblings such as approvals_answer_work_item or approvals_execute_action_on_approval_request, which plausibly also act on work items.

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 on when to reject versus using approvals_answer_work_item or approvals_execute_action_on_approval_request, and no prerequisites (e.g., approver role, work item state). The agent must infer the entire selection logic from the tool name.

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