create_annotation

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

The description includes a '[WRITE][risk=medium]' prefix that explicitly discloses the mutation and risk level, and the 'dry_run' parameter is explained as 'preview without creating.' This adds behavioral context beyond the schema, though it does not mention permissions, rate limits, or side effects after creation.

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?

The description is highly concise: a one-line purpose statement followed by a structured list of arguments. No unnecessary words or repetition. The front-loaded purpose makes the tool's intent immediately clear.

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 simple create tool with no output schema, the description covers all parameters and includes the dry-run safety feature. It lacks details like return value or what happens after creation, but these are not essential given the simplicity. The description is substantially complete for an agent to invoke correctly.

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 0%, but the description provides clear explanations for all five parameters: text, tags, dashboard_uid, dry_run, and target. Each has a concise meaning that goes beyond the schema titles, such as 'Optional dashboard UID to attach the annotation to' and 'If True, preview without creating.'

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?

Description clearly states the action: 'Create a Grafana annotation (an event marker).' The verb 'Create' and specific resource 'Grafana annotation' distinguish it from siblings like create_silence or update_dashboard. The parenthetical 'event marker' adds semantic precision.

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?

No guidance on when to use this tool compared to alternatives. The description only states what it does, without mentioning when to choose it over other creation tools or any prerequisites. It also does not exclude use cases or point to sibling tools.

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