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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds interpretive domain context (a crossing whose thesis predates the filing is a genuine call), but says nothing about auth needs, rate limits, latency, or result volume. Useful but not rich behavioral disclosure.

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-loads the core purpose and keeps the whole thing to a short paragraph. The trailing 'Args: entity' is redundant filler given the schema, which keeps it from being maximally tight, but overall it is efficient and well-ordered.

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, the description carries the burden of explaining returns and does so: a dated sequence of thesis break-condition crossings. It covers purpose, trigger, and interpretation, and only the sibling-alternative routing is left implicit.

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 all three parameters including the reading_level/response_mode interaction are already documented. The description only restates 'Args: entity' and notes response_mode=plain for beginners, adding no syntax or format detail beyond the schema. 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?

Specific verb+resource: a dated track record of each time a filing crossed or held its thesis's break condition, with the notion of a 'genuine call' defined. This is clearly distinguishable from siblings like get_thesis, get_thesis_impact, and what_changed, which an agent could otherwise confuse it with.

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 explicit triggering questions: 'has OptimistFi been right on X' and 'did X's thesis break.' That is clear context for selection. It stops short of naming the sibling alternatives (e.g., get_thesis_impact vs what_changed) that would let an agent disambiguate mechanically.

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