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

With no annotations provided, the description must carry the full behavioral burden. It does disclose a key side effect ('the task stays open') and an identity requirement ('Signed as the requester'). It does not explain permission requirements, whether rejection is reversible, or what happens to the original solution.

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 sentences convey the purpose, consequence, and signing identity with no wasted words. The description is front-loaded with the action and follows with the important behavioral note.

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 simple three-parameter tool with no output schema or annotations, the description covers the core action, a key behavioral consequence, and the responsible caller. It is slightly incomplete in not explaining how rejection relates to accept_solution or whether a reason is required beyond the schema.

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 is the only source of parameter meaning. It adds context for 'reason' ('with a reason') and 'requester' ('Signed as the requester'), but 'taskId' is left entirely to convention and no parameter-level detail is provided.

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 ('Refuse') and resource ('a delivery'), and clarifies that the task remains open. It distinguishes from accept_solution by using 'refuse', though it does not explicitly name the tool's primary resource as 'solution' or connect it to sibling tools.

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 clause 'the task stays open' gives useful contextual guidance about the result of rejection, and 'Signed as the requester' identifies who should call it. However, it does not explicitly state when to use this over accept_solution or mention alternative tools, leaving the usage selection partly implied.

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