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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds genuinely useful context beyond them — the required admin role and the fact that no SEO data provider is called and no credits are spent. It does not, however, state whether the parent report definition survives or whether re-creation is needed.

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?

Three short sentences, purpose first, then the permission prerequisite, then the cost/side-effect note. No filler; each sentence contributes a distinct, actionable fact.

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 two-parameter delete with no output schema and strong annotations, the description covers purpose, gating, and side-effect cost sufficiently. The only minor gap is not telling the agent what happens to the underlying report definition or how to restore the 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% — both projectId and reportDefinitionId are documented in-schema with sourcing hints (list_projects, list_report_definitions). The description adds no additional parameter-level meaning, 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?

Specific verb+resource ("Deletes a report definition's schedule"), which cleanly separates it from the sibling delete_report_definition (the definition itself) and upsert_report_schedule (the writer counterpart). An agent can pick the right 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?

It states a prerequisite (admin role) and that it is free/credit-less, which frames cost and gating, but it never says when to delete a schedule versus using upsert_report_schedule to change it, nor what effect removal has on the parent definition. Usage is implied rather than explicit.

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