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

No annotations exist, so the description carries the full burden. It discloses the feed's content (attacks and victim publications) and a batch requirement, but says nothing about auth needs, rate limits, ordering, or pagination behavior. The claim that batch is 'required' conflicts with the schema, where batch is optional (0 required parameters), which could mislead an agent.

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?

Three sentences, front-loaded with the resource and its contents before usage and the parameter note. The trailing HTTP 200 boilerplate adds little but is compact and conventional.

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 5-parameter, unannotated, no-output-schema tool, the description gives a decent sense of what the feed returns but omits pagination semantics and default behavior, and mislabels batch as mandatory. An agent can call it, but not confidently tune the query.

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 60%; gte and lte are documented in the schema, while page and page_size have no description anywhere. The description only restates the batch format already present in the schema and incorrectly frames it as required, adding no meaning for the remaining four parameters.

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?

States a specific verb and resource ('Get the ransomware feed') and clarifies what the feed contains ('a timeline of attacks and victim publications'). This distinguishes it reasonably from histogram/stats/search siblings, though it never names an alternative explicitly.

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?

'Use to monitor ransomware activity, track groups, and identify victims' gives implied usage contexts, but there is no guidance on when to prefer this feed over siblings like search_ransomware_victims or get_ransomware_attacks_histogram, and no exclusions or prerequisites beyond the batch note.

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