veroq_portfolio_feed

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

No annotations provided, so description must carry the burden. It states returns (holdings summary, ranked briefs), credits cost, and example. Discloses read-only behavior and key output structure adequately.

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?

Extremely concise: one-line action, followed by brief sections (WHEN, RETURNS, COST, EXAMPLE). Every sentence adds meaningful information, no fluff. Front-loaded with purpose.

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?

Though no output schema, description explains return structure and usage clearly. Covers purpose, when-to-use, example, cost. Could add detail on relevance scoring, but current description is sufficient for an agent to understand tool behavior.

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%, so baseline 3. Description adds value by explaining 'ticker/weight pairs' yield impact-ranked coverage, and providing an example that clarifies parameter semantics beyond 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?

Clearly states it retrieves intelligence briefs ranked by relevance to portfolio holdings, using strong verb 'Get' and specific resource. Differentiates from sibling tools like veroq_feed by specifying portfolio context.

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?

Explicit WHEN TO USE section: 'When monitoring news for a specific portfolio.' Provides clear usage context. Lacks explicit when-not-to-use or alternative tools, but guidance is sufficient for an agent.

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