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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is partly covered. The description adds valuable context beyond annotations: it clarifies that rejecting a proposal does not change the plan and that credits are already spent (non-refundable), and it states the authorization scope. It does not describe the response shape, but that is minor for a simple state-change tool.

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 tightly written sentences: the first front-loads the action and state transition; the second supplies the key behavioral and authorization context. No wasted words.

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 single-parameter tool with full schema coverage and no output schema, the description supplies everything an agent needs: the action, the state transition, the fact that nothing else changes, non-refundable credits, and the required role. Nothing material is missing.

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?

There is one parameter ('id') with 100% schema description coverage, so the schema already documents it fully. The description adds no parameter-specific meaning. Per the rubric, high schema coverage yields a baseline of 3 even when the description does not compensate.

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 clearly states a specific verb ('Set a proposal aside') and resource ('proposal'), and adds the state transition (proposed or stale → rejected). It does not explicitly distinguish itself from the sibling apply_agent_run, which is the natural alternative, but the purpose itself is unambiguous.

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 no guidance on when to use this tool versus apply_agent_run or other agent-run tools. The only contextual cue is the role restriction ('Administrator/ProjectManager only'), which is a prerequisite, not usage guidance. An agent must infer that this is the rejection counterpart to apply_agent_run.

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