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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds meaningful context beyond that: an ownership-based authorization constraint and the un-deletable platform-scoped class, which an agent would not otherwise know.

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 with zero filler: the action comes first, followed immediately by the constraint that limits it. Nothing is padded or repeated from the title.

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?

An output schema exists, so return values need no explanation, and the destructive nature plus authorization boundary are covered. It could go slightly further on failure behavior (e.g., deleting a non-owned or nonexistent id), but for a single-parameter delete this is nearly 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?

One parameter with 0% schema description coverage, so the schema supplies only the type and UUID format. The description's 'by id' adds little beyond restating the field name and does not explain where the id comes from or what happens on a mismatched id. Baseline 3 given a single, self-evident identifier.

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 and resource ('Deletes a chart annotation by id'), which is unambiguous against the annotation siblings (create_annotation, update_annotation, list_annotations). It does not explicitly contrast itself with those siblings, but the operation's nature makes the differentiation obvious.

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?

Provides an explicit precondition and exclusion: only user-owned annotations can be removed, and platform-scoped annotations cannot be deleted via this tool. It stops short of naming an alternative path for platform-scoped deletions or clarifying when deletion is preferable to updating.

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