get-event-subscription

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

No annotations provided, so description bears full burden. It only states 'Get event subscription details' implying a read operation, but omits any side effects, required permissions, or limitations. The optional parameters (fields, include) are not mentioned in context.

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?

One concise sentence of 6 words, conveying the core purpose. While brief, it is not overly concise to the point of obscurity; it strikes a reasonable balance for a simple retrieval tool.

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?

No output schema, missing behavioral details (return format, error handling, rate limits). For a read tool with sibling by-name variant, more context would be helpful. The description is insufficient for comprehensive understanding.

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% (descriptions for id and include; fields has a description in schema). The description adds no additional meaning beyond what the schema provides. 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 'Get event subscription details by UUID' clearly states the action (get details) and resource (event subscription) with a specific identifier method (UUID). It distinguishes from the sibling tool 'get-event-subscription-by-name'.

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 versus alternatives (e.g., when to use by-name variant), no prerequisites, and no when-not-to-use context. The description is minimal and does not help the agent choose.

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