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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds real behavioral context beyond that: it defines 'compliant' vs 'debt_compliant' semantics, explains the null case (business needs a closer look) and the borderline flag within one percent of a threshold. It does not mention data freshness/latency or error behavior, but the semantic disclosure is substantial.

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?

Purpose is front-loaded, then field semantics follow in a dense but information-bearing block justified by the absence of an output schema. The trailing name-fallback sentence feels tacked on, but overall there is little waste and no repetition.

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 entire return-value burden and does so: it enumerates the returned fields and clarifies the ambiguous verdict fields. The only parameter is documented and annotations cover safety, so nothing needed to call it correctly 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 coverage is 100% and the single parameter is fully described in the schema, including the name-fallback behavior. The description's closing note ("A company name (for example nvidia) also works") merely restates that schema hint, so it adds little beyond structured data — baseline 3.

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+resource+scope ("Screen one company against all four standards"), and the singular "one company" scope cleanly separates it from the sibling screen_portfolio. An agent can tell what it does and which sibling it is not without opening any 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 only implied: an agent can infer this is for a single-company check and screen_portfolio is for a portfolio, but the description never names alternatives or states when-not to use this. No prerequisites, exclusions, or routing guidance are given.

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