get-event-subscription

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

No annotations are provided, so the description carries full burden. It only states 'Get details', implying a read operation, but lacks any information about permissions, side effects, rate limits, or whether the tool is read-only. This is insufficient for a tool without annotations.

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 one sentence, which is concise. However, it is overly brief and fails to include important details, earning a middle score for conciseness.

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?

Given there is no output schema and no annotations, the description should compensate by explaining what details are returned. It does not, leaving the agent uncertain about the response structure. The description is incomplete for a tool with 3 parameters and no output schema.

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% (2 out of 3 parameters have descriptions). The tool description does not add any additional meaning to the parameters; it merely restates the general purpose. The 'include' parameter lacks a schema description and the tool description does not explain its values.

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 clearly specifies the action (Get), the resource (event subscription details), and the unique identifier (by UUID). It distinguishes from the sibling tool 'get-event-subscription-by-name' which retrieves 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?

The description implies the tool should be used when you have a UUID. It does not explicitly mention alternatives or when not to use it, but the purpose is sufficiently clear for an agent to infer usage context.

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