Veroq

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

With no annotations provided, the description carries the full disclosure burden and effectively communicates the COST ('1 credit') and detailed RETURN structure ('title, ticker, tier, creation date, and markdown content'). It misses error handling details (e.g., behavior if ID doesn't exist), but covers cost and output format which are essential for agent planning.

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?

Uses a highly structured format with clear section headers (WHEN TO USE, RETURNS, COST, EXAMPLE) that makes the description scannable. Every sentence serves a distinct purpose; there is no redundant or filler content. The core action is front-loaded in the first sentence.

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 single-parameter retrieval tool without an output schema, the description is complete. It compensates for the missing output schema by detailing the full return structure and includes cost information necessary for agent decision-making. Given the tool's simplicity, no additional context is required.

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%, establishing a baseline of 3. The description adds value beyond the schema by providing a concrete JSON EXAMPLE showing the expected 'report_id' format ('rpt_abc123'), which helps the agent understand the parameter structure better than the generic schema description alone.

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 a specific verb ('Retrieve') and resource ('previously generated report'), clearly defining the tool's scope. It explicitly distinguishes itself from the sibling 'veroq_generate_report' by stating it fetches 'completed report content,' establishing the critical workflow relationship between these two tools.

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?

Provides explicit 'WHEN TO USE' guidance stating it should be used 'After calling veroq_generate_report.' This clearly defines the prerequisite and sequencing logic, preventing the agent from attempting to retrieve reports that haven't been generated yet.

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