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

Annotations declare readOnly and idempotent. Description adds that mark_read:true flags events so next call shows newer ones, explaining the side-effect beyond a simple read. No contradiction with 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?

Four concise sentences with no redundancy. Primary purpose stated first, then details, then polling guidance. Every sentence adds value.

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?

For a filtered list tool with comprehensive annotations and schema, the description covers return fields, filter options, side effects of mark_read, and alternative access. No output schema needed since return is clearly described.

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 100%, but description adds practical examples: 'Filter by type (e.g. "sec_8k") and/or since (ISO timestamp)' and explains mark_read's effect. This supplements the schema descriptions well.

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 opens with 'Pull fired events from your subscription feed', clearly stating the action and resource. It specifies the return includes 'source, citation_uri, and raw event payload', distinguishing this tool from siblings like subscribe/unsubscribe and other data retrieval 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?

Provides usage context with 'Polls work fine' and mentions an alternative endpoint for scripts/dashboards. While it doesn't explicitly state when not to use, the alternative guidance is helpful for deciding between tool and direct HTTP access.

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