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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful non-annotation fact ('Needs your API key'), but it does not disclose what happens to the request after a decline or how the caller should retry.

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 with no filler; the core action is front-loaded and the API-key requirement is appended compactly.

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 low-complexity mutation with 3 parameters, complete schema descriptions and existing safety annotations, the description covers purpose, scoping and auth. It omits post-decline effects, but the absence of an output schema and the annotation coverage keep this close to complete.

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 100%, so side, caseId and idempotencyKey are fully documented in the schema, which sets the baseline at 3. The description's 'on the given side' merely echoes the schema's enum rather than adding format or constraint detail.

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+resource ('Decline a request for counsel') with the scoping condition 'that names you, on the given side'. It is distinguishable from the sibling accept_counsel_request by the verb, though it never names alternatives explicitly.

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 phrase 'that names you' implies the precondition (you must be the named counsel), but there is no explicit when-to-use or when-not-to-use guidance versus accept_counsel_request or withdraw_as_counsel. Usage is implied rather than stated.

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