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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that this is a composite read aggregating three views in one call, but says nothing about latency, rate limits, data freshness, or when the composite is preferable to fetching pieces via get_filings/get_thesis.

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 payload summary, then triggers, then the exclusion, then args – a sensible priority order with no filler prose. The trailing 'Args: entity; response_mode.' is redundant with the schema and slightly incomplete, which keeps it just short of 5.

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?

There is no output schema, so the description carries the return-value burden and does name the three content blocks the agent will get back. Combined with annotation coverage of the safety profile, an agent has enough to call this correctly, though it lacks guidance on output size or multi-entity behavior beyond the compare pointer.

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 the schema already fully documents entity, reading_level, and response_mode, making baseline 3 appropriate. The description only restates response_mode=plain for beginners and its 'Args' line even omits reading_level, adding little beyond the structured fields.

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 concrete verb+resource ('a stock's full read in one call') and enumerates the three payload components: standing investment case, valuation off filed financials, and latest quarter. It explicitly names the sibling it is not ('several companies → compare'), so an agent can route without opening a schema.

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 when-to-use triggers in the user's own phrasing ('is X a buy; is X cheap; what are X's earnings; how was X's quarter; did X beat') and an explicit exclusion with the alternative tool ('Not for: several companies → compare'). Nothing is left to inference.

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