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

The description discloses that mark_read:true modifies the feed state (flags events read), which contradicts the annotation readOnlyHint: true. According to the rules, a score of 1 is given when the description contradicts annotations. Annotation contradiction is flagged.

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 concise paragraph that front-loads the main purpose and then elaborates on key details. Every sentence adds value with no redundancy, making it efficient and well-structured.

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 description covers the main functionality (retrieval, filtering, mark_read behavior), explains return fields (source, citation_uri, raw payload), and provides an alternative access method. Given no output schema, it adequately addresses the tool's usage and output.

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?

The description adds value beyond the schema by providing examples for 'type' (e.g., 'sec_8k'), clarifying that 'since' is an ISO timestamp, and explaining the effect of 'mark_read'. With 100% schema coverage, the description enriches the parameter semantics.

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 states the verb 'Pull' and the resource 'fired events from your subscription feed', and explains what each alert carries. However, it does not explicitly differentiate from sibling tools like recent_changes or list_subscriptions, though the context is sufficiently distinct.

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 some usage guidance, noting that polls work fine and offering an alternative URL. However, it lacks explicit when-to-use or when-not-to-use instructions compared to other tools, and does not cover prerequisites or exclusions.

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