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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description usefully adds that the call is FREE (database only, no SEO provider, no credits) and that it returns `{ widgetCount }`. It does not state what happens to widgets omitted from the new list or any auth requirements, but the cost/return disclosure is meaningful context beyond annotations.

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 tight sentences: the core action and scope are front-loaded, followed by return shape and cost. Every clause earns its place with no padding.

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 list-replacement mutation, the definition gives scope, return shape, and cost behavior, and the schema fully documents parameters while annotations cover safety. Minor gaps remain (behavior on an empty list, the maxItems=11 bound), but nothing essential to calling it correctly 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 coverage is 100%, so all three parameters are already documented in the schema, including print order and the widget-type catalogue. The description's 'in print order' restates the schema's own wording and adds no new syntax or format detail, so baseline 3 applies.

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 (Replaces) plus resource (a report definition's whole widget list) and scope (whole list, print order). This cleanly separates it from siblings like create_report_definition, rename_report_definition, and get_report_definition without the reader opening a 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?

The phrase 'whole widget list' implicitly tells the agent this is a full-replacement operation rather than an append, which is useful. However, it names no alternatives and gives no explicit when-to-use or when-not-to-use guidance relative to create/rename/render report-definition siblings.

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