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

With annotations covering safety (readOnly, idempotent, non-destructive), the bar is lower, but the description goes further by detailing the return payload: say sentence, live price, consolidated share count, filing figures, business screen, per-standard ratio/threshold/verdict, and borderline flagging. It explains the semantics of 'compliant' vs 'debt_compliant' and the null case, which is real behavioral context beyond the annotations.

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 purpose, then dense enumeration of return fields. Long but every sentence carries information; only the leading 'Mizan.' label is throwaway.

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?

No output schema exists, so the description carries the full burden of describing returns, and it does so thoroughly, including the meaning of key fields and the borderline-verdict flag. Nothing an agent needs to call or interpret the tool 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 there is a single required parameter, so the baseline is 3. The description adds that a common company name (e.g. nvidia) works in place of a ticker, which extends the schema's 'US listing symbol' description.

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 ('screen') and resource ('one company') plus the scope ('against all four standards'), which cleanly distinguishes it from the sibling mizan_screen_portfolio. An agent can tell what it does 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?

The scope word 'one company' implies single-entity use versus the sibling portfolio tool, but there is no explicit when-to-use/when-not guidance or named alternative. Usage is inferable but not spelled out.

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