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

Even though annotations already declare readOnlyHint and idempotentHint, the description adds substantial behavioral detail beyond that: it explains that unknown exposure returns both branches, that kev_feed indicates which branch reproduces CISA's due date, that a row is a mapping and no agency enumeration date is returned, and the meaning of basis values. This is extra transparency about what the tool actually does and returns.

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 dense paragraph, but it is efficiently front-loaded with the essential purpose first, then expands into details that each earn their place. No filler or repetition exists. The flow from purpose to data provided to field clarifications is logical and compact given the complexity of the tool.

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?

Given the tool's moderate complexity and the absence of an output schema, the description covers all necessary aspects: the input parameters, the returned fields (KEV status, due date, SSVC values, triage flag, row, timeline, kev_feed, fix/detection state, lanes), the basis explanation, and a key limitation (no agency enumeration date). An agent has enough context to invoke the tool correctly.

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 schema already covers 100% of the parameters with descriptions, but the description adds significant semantic nuance: it explains the effect of exposure values (yes/no/unknown, with unknown returning both branches), the max count of 50 CVEs, and what the 'basis' field means relative to each CVE's status. This goes well beyond the schema's basic descriptions.

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 'BOD 26-04 Table 1 read for up to 50 CVEs at a stated asset exposure,' which clearly states the verb (read), the specific resource (BOD 26-04 Table 1), and the scope. It distinguishes the operation from sibling tools like search_cves or get_cve by focusing on a specific BOD dataset and the exposure parameter.

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 clearly implies when to use it: to read Table 1 data for a set of CVEs given an asset exposure. It does not explicitly state when not to use it or name alternative tools, but the context is unambiguous. It explains the inputs and behavior sufficiently for an agent to decide it is the right tool for BOD 26-04 table reads.

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