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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds context annotations do not carry: the operation is database-only, invokes no SEO data provider, and consumes no credits. It does not say whether the deletion is permanent or what happens to dependent report schedules.

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 sentences, zero filler, with the core action front-loaded and the cost consequence immediately after. Every clause carries information an agent can act on.

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 destructive, annotation-covered delete with no output schema, the description covers cost behavior but omits cascade/reversibility facts, notably whether associated report schedules are also removed. Adequate but with a clear gap given the sibling delete_report_schedule.

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% and both parameters are fully documented in the schema, including the 'Required.' marker and pointers to list_projects and list_report_definitions. The description adds nothing about either parameter, so the 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 precise verb+resource ('Deletes a report definition'), which cleanly separates it from get_report_definition, rename_report_definition and render_report_definition. It does not explicitly name the nearest confusable sibling, delete_report_schedule, so an agent must rely on the resource noun alone to distinguish the two deletions.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The 'FREE' note does give a decision-relevant cost signal (no credits spent), which helps an agent route among operations, but it is not usage guidance in the strict sense.

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