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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: the 15-holding cap, the fact that all four standards are applied, and the three outputs returned (compliance share per standard, failing holdings, combined dividend purification ratio).

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?

Two compact sentences, front-loaded with the purpose and then the scope and outputs. Every clause carries information; nothing is padding or restated from the title.

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 usefully enumerates the return payload, and the single input is documented. The main remaining gap is edge behavior (what happens when more than 15 holdings are supplied, or how unweighted holdings are treated), which an agent would want before calling.

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 documented by the schema, giving a baseline of 3. The description adds meaning the schema does not carry: the maximum of 15 holdings that may be passed, which is a real constraint on how the parameter is populated.

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?

The description states a specific verb ('Screen') and resource ('a whole portfolio'), and the scope qualifier 'up to 15 holdings under all four standards' separates it in practice from the single-entity sibling screen_company. It does not explicitly name or contrast any sibling, so it falls just short of the top band.

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 the tool for batch screening a set of holdings rather than one company. There is no statement of when to prefer it over screen_company, no preconditions, and no exclusions (e.g. what to do with more than 15 holdings).

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