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

Annotations already establish the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's added value is the auth requirement (write key, member or higher), which is genuinely useful and not in the annotations. It doesn't state whether the annotation is editable, removable, or visible to other members, so not a 5.

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 waste. The action and its object lead, and the authorization constraint follows without 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 3-parameter, all-required mutation with no output schema, the description covers the action, the content, and the auth gate. It could still say whether the annotation can later be modified or deleted, but nothing critical to invoking it correctly is absent.

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 67%: date carries its YYYY-MM-DD format and site_id points to list_sites, but text is undocumented. The description partially compensates by giving example annotation content (release, campaign, outage), clarifying what text should hold, but does not add format or sourcing detail for the other parameters.

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 ('Mark a date on the charts') and grounds it with concrete examples (release, campaign, outage). No sibling tool competes for this job, so the purpose is unambiguous even without explicit sibling differentiation.

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 a clear context for use (annotating releases, campaigns, outages) and states the access prerequisite: a write key plus member access or higher. It stops short of naming when NOT to use it or any alternative tool, so it falls short of a 5.

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