Creating a new report subscription

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

Annotations already provide readOnlyHint=false, destructiveHint=true, but the description adds the permission requirement 'Perm: view_reports', which is useful. However, the description adds no further behavioral context beyond what the annotations and name imply, such as side effects or idempotency.

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 contains two sentences: a heading 'Creating a new report subscription.' followed by the same phrase 'Creates a new report subscription.' This redundancy wastes space. It could be simplified to a single concise sentence or bullet points.

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?

While an output schema exists so return values are covered, the description omits crucial context: what triggers a subscription (e.g., email, frequency), how dry_run works, and why confirm=YES is required. For a destructive operation (destructiveHint=true), more safety guidance would be expected.

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%, so parameters are documented in the schema. The tool description does not add any extra meaning for parameters (body, confirm, dry_run). The mention of 'Perm: view_reports' is not parameter-specific. Baseline 3 is appropriate.

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?

The description states the action 'Creating a new report subscription' and mentions the required permission 'view_reports'. While it distinguishes the tool from siblings by specifying 'report subscription', the wording is redundant ('Creating... Creates...') and lacks precision on what a subscription entails.

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 is provided on when to use this tool versus alternatives (e.g., update_report_subscription, delete_report_subscription, list_report_subscriptions). There is also no explanation of how to choose between dry_run and confirm parameters.

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