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

No annotations provided, so the description carries full burden. It discloses that the feed is cursor-paginated, filtering available, and that records are observational public records. There are no contradictions, and no destructive actions are implied.

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 brief yet informative, front-loaded with a question that captures purpose, then specifics. Every sentence adds value, and the price note is appended efficiently. No unnecessary 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?

The tool has 7 optional parameters and no output schema. The description explains the output fields, ordering, pagination (cursor, cap), and price. It lacks explicit mention of response structure (e.g., presence of 'next_cursor'), but is otherwise complete for a feed tool.

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 100%, so baseline is 3. The description adds context by explaining output fields, pagination, and filtering capabilities (state, NAICS, certification, VA award, since). It also mentions the price per row, which is not in schema.

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 that the tool provides a feed of SDVOSB/VOSB vendors with recent federal traction, sorted newest-first by award date. It lists specific output fields (vendor, state, NAICS, certification, award totals) and distinguishes from siblings by focusing on veteran-owned vendors and feed format.

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 implies usage for identifying set-aside-eligible vendors for teaming/growth targets. It mentions filterability and price, but does not explicitly compare to sibling tools or state when not to use. Still, the context is clear.

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