briefing_stock_fetch

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

With no annotations, the description carries full responsibility for behavioral disclosure. It notes the conditional ticker behavior and the post-fetch pipeline, but does not state whether the operation is read-only, what the return payload is, or any side effects/authentication requirements beyond schema info.

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 two compact sentences, front-loads the core purpose, and includes trigger phrases and the follow-up call without wasted words. Every clause adds value.

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?

Given no annotations and no output schema, the description should cover more ground. It explains role, triggers, and next step, but omits return format, persistence, error handling, and other caveats. It is adequate for a simple fetch, but not fully complete.

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?

All parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds a bit by reinforcing the 'no tickers = whole watchlist' behavior, but largely repeats schema content without deeper semantics for token or hours_back.

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 the tool fetches the latest news for followed stocks, using a specific verb and resource. It also provides example user intents and implicitly distinguishes itself from siblings by focusing on the watchlist and pairing with briefing_stock_digest.

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 trigger phrases are provided, and the behavior with/without tickers is clearly explained. It also gives a follow-up action (call briefing_stock_digest), but does not explicitly name alternative tools or exclusion criteria, so it falls short of a 5.

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