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

With no annotations provided, the description carries the full burden of disclosing behavior. It clearly states 'immutable once saved', which is critical behavioral context—an agent knows a save can't be undone. It also states the function returns the generated card. However, it does not disclose whether generation overwrites, requires approval, or has side effects on fund state beyond immutability; still, for a single-arg generator, the main side-effect (immutable creation) is disclosed.

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 description is compact and front-loaded: the first sentence conveys the action and the immutable constraint. The Args line is redundant with the schema but serves as a quick reference. There is no wasted prose; every sentence adds value.

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?

Given a single-parameter tool with an output schema, the description covers the critical behavior (immutable save) and return. It doesn't explain why the card is immutable or what grades/analysis entail, but the output schema presumably fills in the return structure. For a simple generator tool, this is nearly complete; the only missing piece is when to invoke it over alternatives, but that falls under usage guidelines.

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?

The schema has one parameter and is 0% documented, meaning the schema provides no description for 'fund_id'. The description does repeat 'fund_id: The fund's ID' in the docstring, which adds minimal meaning beyond the schema (type integer). It doesn't specify where to find the ID or validation constraints. Baseline for 1 param with 0% coverage would be low, but the description at least identifies it; however it adds no semantic depth beyond the docstring.

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 ('Generate'), resource ('fund report card'), and a key distinguishing constraint ('immutable once saved'). This clearly differentiates it from the sibling get_fund_report_card (which retrieves an existing card) and other fund-related actions.

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 purpose is clear but there is no explicit guidance on when to generate a new card vs. using the existing get_fund_report_card, nor are there prerequisites or consequences stated. The immutability note implies a caution but doesn't state 'use get_fund_report_card to retrieve the existing one' or warn that regenerating is impossible.

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