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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real context on what the record contains (break-condition filings, trailing-year early warnings) and recommends response_mode=plain for beginners, but says nothing about what happens when a company has no thesis, how far back the history goes, or any limits on the result.

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 content definition is front-loaded and the usage triggers follow immediately, with no filler sentences. The opening sentence is dense and jargon-laden ('crossed or held its thesis's break condition'), which costs a little readability but every clause carries information.

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 three-parameter analytical read with no output schema, the definition explains the conceptual shape of the return (dated calls plus early warnings) well enough to set expectations. The gaps are edge-case behavior – unresolvable entity, no-thesis companies, empty history – which are secondary for this tool.

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 description coverage is 100%, so entity, reading_level, and response_mode are already fully documented, including the enum values and the default of 13. The description's 'Args: entity' and 'response_mode=plain for beginners' restate rather than extend the schema, so baseline 3 applies.

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?

Names a specific resource (a company's dated track record) and defines its contents precisely: filings that crossed or held a thesis break condition, plus early_warnings from the latest 10-Q trailing year. That scope distinguishes it from siblings like get_thesis, get_filings, and what_changed, though the verb is only implied by the tool name.

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?

Gives concrete trigger questions ('has OptimistFi been right on X', 'did X's thesis break') that tell an agent when to reach for this tool. It does not name an explicit alternative or when-not condition, but the query examples are clear enough to route correctly in most cases.

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