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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description goes further, disclosing non-obvious behavior: 'compliant' is overall verdict and becomes null when the business needs review, 'debt_compliant' is the debt test alone, and verdicts within one percent of a threshold are flagged borderline.

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 purpose is front-loaded in the first clause, followed by a dense but tight enumeration of return fields and their semantics. It is appropriately sized for a tool with no output schema, though the long parenthetical about 'compliant' could be trimmed slightly.

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 a single well-documented parameter, the description carries the full disclosure burden and does so thoroughly: it names every returned field, the per-standard ratio/threshold/verdict, and the meaning of the null/borderline cases. Nothing needed to interpret the result is missing.

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 documents the single 'ticker' parameter. The description's note that a common company name (e.g. nvidia) also works largely duplicates the schema's 'a common company name also works', adding no new syntax or format detail, so the baseline of 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?

States a precise verb and resource ('Screen one company against all four standards') and names the exact scope ('one company'), which cleanly distinguishes it from the sibling screen_portfolio. An agent can tell the two apart without opening the 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?

Usage is implied by the scope word 'one' against the sibling 'screen_portfolio', so the single-vs-many selection is inferable. However, there is no explicit when/when-not statement, no mention of prerequisites, and no direct routing to the sibling alternatives.

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