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

Goes well beyond readOnlyHint: it discloses that the response shape changes based on arguments (ticker-only vs free-text), that sentiment is a label not a number, that matching is prefix-word rather than semantic, the limit defaults and hard cap, absence of pagination, the cron-populated multi-provider source, and that caveats ride in tool_notes. This is exactly the extra behavioral context annotations do not provide.

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?

Front-loaded with the core purpose, then layered with constraints in diminishing priority. Dense but each clause carries information; the all-caps emphasis is stylized but signals the important conditional. Slightly packed.

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?

With no output schema and no annotations beyond readOnlyHint, the description carries the burden and does so well, covering response shape, matching, limits, and where caveats live. Minor gap: it doesn't clarify when to prefer this over search_news_archive.

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% (baseline 3), and the description still adds real meaning: it explains that the choice of parameters changes the response shape, clarifies query is prefix-word not semantic, and reiterates the limit cap. That raises it above the schema-only baseline.

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?

States a specific verb and resource ('Read the Oxford Ledge news archive'), its filter axes (ticker and/or keyword), and its ordering (newest first). Clear on its own, but it never names or distinguishes itself from the very similar sibling search_news_archive, leaving the agent to infer the split.

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?

Use is implied by 'by ticker and/or keyword' and the note about handling both response shapes, but there is no explicit when-to-use, when-not, or alternative (e.g. search_news_archive). Guidance is present but must be inferred.

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