veroq_feed

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

No annotations provided, but description discloses returns (array with fields), cost (1 credit), and example. Does not mention pagination or rate limits, but is sufficient for a read-only feed.

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?

Structured with targeted sections: header, WHEN TO USE, RETURNS, COST, EXAMPLE. Every sentence is informative and no redundancy.

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?

Specifies return type and fields, cost, and usage example. No output schema, but description covers essentials. Could mention pagination or error conditions, but adequate for a simple feed.

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% with descriptions. Description includes an example using 'category' and 'limit', which adds practical usage context but does not significantly surpass 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?

Explicitly states 'Get the latest verified intelligence briefs in reverse-chronological order' and distinguishes from sibling by mentioning browsing without a query vs. searching with a topic.

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 clear WHEN TO USE section: 'For browsing recent news without a specific search query. Use veroq_search when you have a topic in mind.' This directly guides tool selection.

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