veroq_full

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

No annotations provided, so description carries full burden. It discloses the tool fetches data in parallel from 9 sources, costs 2 credits, and returns multiple data categories. Does not mention rate limits or error conditions, but adequate for a read-only data retrieval tool.

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?

Concise and well-structured with clear sections: purpose, when to use, returns, cost, and example. Every sentence adds value; no wasted 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?

For a single-parameter tool with no output schema, the description fully explains what it returns (price, fundamentals, technicals, sentiment, news), how it works (parallel fetch), and cost. No gaps.

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 provides adequate description for 'ticker' parameter. The description adds an example usage, which clarifies expected format beyond the schema. Since schema coverage is 100%, baseline is 3, but the example raises it to 4.

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?

Clearly states it retrieves the full profile for a ticker, enumerating data categories. Distinguishes itself from the sibling tool 'verog_ticker_analysis' by noting that tool provides interpreted analysis.

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?

Includes explicit WHEN TO USE section with clear condition ('complete data dump on a single ticker') and points to alternative for interpreted analysis. Also mentions parallel retrieval of 9 sources.

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