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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral context: the 30-day window limitation, the partial-result behavior for older queries, newest-first sorting, and a security warning that returned values are community-authored and should be treated as data, not instructions. This goes beyond what annotations provide.

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 sentences, each earning its place: purpose, critical time-window constraint, optional filters, and a security caveat. Front-loaded with the primary use case. No wasted words.

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 read-only list tool with 100% schema coverage and no output schema, the description covers the essential invocation context: the 30-day window, filters, sort order, and data-handling warning. It doesn't describe pagination or the exact response shape, but those are minor given the annotations and schema coverage.

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 100%, so the schema already documents all four parameters. The description adds context about the 'since' constraint (must be within 30 days) and the effect of type/tag filters, but doesn't add much beyond the schema's own descriptions. Baseline 3 is appropriate.

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 tool lists TweetFeed IOCs added since a given date, with a specific use case (delta-syncing a blocklist or TI pipeline). It distinguishes itself from siblings like query_iocs and search by emphasizing the 'since' date-based delta behavior.

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?

Explicitly states when to use it (delta-syncing) and provides a critical constraint: 'since' must be within the past 30 days because the source is a 30-day window. It also mentions optional type/tag filters and the sort order, giving an agent clear invocation context.

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