veroq_research_bills

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

No annotations provided, but the description compensates fully: it states that the tool returns a list of bills with specific fields, and mentions 'COST: 1 credit.' There is no destructive behavior implied. The description is transparent about output and cost.

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 extremely concise: two lines of purpose, a short 'WHEN TO USE' sentence, one line for returns, one for cost, and an example. Every sentence is necessary and informative. No extraneous text.

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 that the tool has no parameters and no output schema, the description provides all needed context: purpose, usage scenario, return format, cost, and a sample invocation (empty object). It is fully sufficient for an agent to decide when to call this 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?

Input schema has zero parameters, so schema description coverage is 100% trivially. The description adds value by specifying the return data ('title, sponsor, status, introduced date, and summary'), which helps the agent understand what will be received. Since no parameters exist, the description's clarification of output is essential.

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?

Description clearly states the tool returns 'Recent Congressional bills — legislation that may affect markets.' It identifies the specific resource (Congressional bills) and purpose (market-impact analysis). The sibling tools like veroq_research_fda and veroq_research_github are distinct domains, so differentiation is clear.

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?

Has an explicit 'WHEN TO USE' section: 'To track new legislation in the US Congress that could impact industries or markets. Good for policy risk analysis.' This directly tells the agent the appropriate context. No need for when-not because the use case is narrow.

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