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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds genuinely new, non-obvious behavior: a report cannot be read back, edited, or withdrawn once sent, and it requires a confirmation gate. That is the key trait an agent must know for a one-way write, though it does not discuss failure modes or rate limits.

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?

Front-loads the identity of the tool and then the critical confirmation constraint; every sentence carries actionable content. It is somewhat dense with imperatives but nothing is wasted, and the docs link is a reasonable trailing pointer.

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?

With no output schema and annotations covering only the safety profile, the description supplies everything an agent needs: scope, mandatory confirmation flow, irreversibility, and parameter construction guidance. Nothing required for correct invocation 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?

Schema description coverage is 100%, so the baseline is 3. The description goes further by illustrating the path format (/projects/{id}) and instructing what message should contain ('what went wrong and what was expected'), adding usage meaning beyond the schema's terse field descriptions.

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 precise verb+resource ('report a problem with Pizza Developer itself') and explicitly scopes out the alternative interpretation ('the app, not a project tracked inside it'), which separates it from project/workflow siblings such as report_workflow_step. An agent can identify the tool without opening the schema.

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?

Gives explicit when/when-not rules: never send on your own initiative, show the exact message and path first, and call only after explicit user confirmation with userConfirmed: true. It also says when to include path (a particular page like /projects/{id}), so the routing and precondition logic is complete.

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