veroq_get_report

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

No annotations are provided, so the description carries the full burden. It discloses the cost (1 credit) and describes the return structure (title, ticker, tier, date, markdown). While it doesn't mention error handling or rate limits, these are less critical for a simple retrieval tool. The transparency is good but could be slightly more comprehensive.

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 highly concise: four short lines covering purpose, usage, returns, cost, and example. Every sentence earns its place, and the use of labeled sections (WHEN TO USE, RETURNS, COST, EXAMPLE) makes it easily scannable.

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 one-parameter retrieval tool with no output schema, the description is complete. It tells the agent what the tool does, when to use it, what it returns, its cost, and provides an example. No gaps remain for correct selection and invocation.

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 input schema has 100% coverage with a description for report_id. The description adds value by providing an example value ('rpt_abc123') and the context that the ID comes from generation. This goes beyond the schema's bare description.

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 'Retrieve a previously generated report by its ID.' The verb 'retrieve' with the specific resource 'report by ID' makes the action unambiguous. It distinguishes itself from sibling tool veroq_generate_report by implying this is for fetching after generation.

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 explicitly provides usage context: 'WHEN TO USE: After calling veroq_generate_report, use this to fetch the completed report content.' This clearly tells the agent when to invoke this tool versus alternatives, and it gives an example input.

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