subscribe_events

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

No annotations are present. The description only says 'subscribe' without explaining subscription behavior (e.g., persistence, overwrite, side effects). Critical behavioral traits are missing.

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 a single sentence, front-loaded. However, it is too brief and could achieve more with minimal length. It is not verbose but under-informative.

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 tool is simple with 2 parameters and an output schema, but the description lacks details on subscription lifecycle, response format, or side effects. It leaves significant gaps for an agent relying on the description alone.

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%, yet the description fails to add meaning to the parameters. It mentions 'specific event types' but doesn't clarify agent_name or event_types, nor their roles or constraints.

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 name 'subscribe_events' and description clearly state the verb 'subscribe' and resource 'event types' on the Event Bus. It distinguishes from sibling tools like publish_event and poll_events by focusing on subscription.

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 (e.g., poll_events). No context, prerequisites, or exclusions are mentioned.

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