list_event_subscriptions

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

No annotations exist, so the description carries full responsibility. It fails to disclose any behavioral traits beyond the basic listing action, such as whether it returns paginated results, requires special permissions, or includes deleted subscriptions by default. The parameter 'include_deleted' is in the schema but not explained.

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 extremely short (one sentence), which could be seen as concise, but it omits necessary information. It is not structured with any detail beyond the bare minimum, so it does not earn a higher score.

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 the tool has 4 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what an event subscription is, how results are ordered, or how to interpret the output. The context from sibling tools is not leveraged. A complete description would address these gaps.

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%, and the description does not mention any parameters. The agent must infer the meaning of 'limit', 'offset', 'fields', and 'include_deleted' from names alone, which is insufficient for correct usage. The description provides no added semantic meaning.

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 'List event subscriptions' clearly states the verb and resource, making the basic purpose understandable. However, it lacks specificity to distinguish it from other list tools or explain what an event subscription is, missing the mark for a higher score.

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 provides no guidance on when to use this tool versus alternatives like 'get_event_subscription' or 'get_event_subscription_by_name'. There is no mention of pagination, filtering, or intended use cases, which leaves the agent without crucial context for selection.

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