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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Collect' and 'Auto-assesses' but does not clarify whether this is a read-only operation, what 'auto-assesses' entails, whether it persists data, what side effects occur, or any authentication/rate-limit constraints. This is a significant gap for a tool that could have mutation implications.

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 two terse sentences, front-loaded with the primary verb and resource, and every word earns its place. It is concise without being under-specified for the purpose it serves.

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 has no output schema and no annotations, yet the description does not explain the return format or what 'auto-assesses' produces. The single optional parameter is covered, but the overall context of what the agent receives after invocation is missing. Given the simple parameter set, more clarity on output and assessment behavior is expected.

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% for the single optional parameter entity_id, which the schema describes as 'Entity ID (optional)'. The description adds no additional meaning to this parameter beyond the schema. Baseline of 3 is appropriate since the schema already provides sufficient 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 a specific verb ('Collect') and resource ('live Art. 10 evidence') from named sources (NVD, CISA KEV, CERT-Bund), and adds the distinct 'Auto-assesses' behavior. This distinguishes it from sibling tools like evidence_pack or freshness_check, which focus on packaging or checking rather than live collection from these specific sources.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies usage when fresh evidence is needed, but there is no mention of exclusions, prerequisites, or references to sibling tools. The absence of any 'when to use' context leaves the agent without clear decision support.

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