get-subscription

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

Annotations already cover readOnlyHint=true and destructiveHint=false. The description adds value by naming the specific fields returned (resource, changeType, notificationUrl, expirationDateTime, applicationId) and pointing to the Permissions section for supported resources. This provides context beyond the annotations without contradiction.

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 two short sentences plus a concise tip. It front-loads the core purpose and then provides a useful shortcut. No redundant phrasing; every sentence contributes to understanding.

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?

The description explains the return fields, mentions permissions context, and gives the id-finding workflow. Given the read-only hint and the thorough parameter schema, the description is complete enough for an agent to call this tool correctly, though it doesn't detail output structure (no output schema exists).

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?

The input schema has 100% coverage of parameters with detailed descriptions (e.g., subscriptionId is described as a path segment with explicit naming guidance). The tool description doesn't add extra parameter semantics beyond what the schema already explains, so the baseline of 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 a specific verb ('Retrieve') and resource ('a subscription'), and differentiates itself from siblings by explicitly saying 'Gets a specific webhook subscription by id' and referencing list-subscriptions to find the id. This clearly separates it from the listing and mutation tools.

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?

The tip 'Use list-subscriptions to find the id' gives direct guidance on when to use this tool versus its sibling for listing. It doesn't explicitly exclude other tools (e.g., update or delete), but the focused use case is clear. A small deduction for not explicitly stating when not to use this tool.

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