List financial years

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

Discloses that the tool is read-only (consistent with readOnlyHint=true) and lists the output includes status (open/closed/lodged) and dates. No contradictions with annotations; adds behavioral context beyond the annotation.

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 concise sentences with no wasted words: first states the action and output, second gives usage guidance. Perfectly front-loaded and to the point.

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 no output schema, the description still mentions output fields (status, dates) and the parameter is well-documented in schema. Lacks details on edge cases (e.g., no financial years) but sufficient for a simple list tool.

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 has 100% description coverage for the single parameter fund_id, which already explains its purpose. The description adds no additional semantics beyond the schema, so baseline 3 is appropriate.

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?

Clearly states it lists financial years for a fund, including status and dates, and explicitly distinguishes from sibling tools like close_financial_year or lodge_financial_year by noting its use to find the year label.

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?

Explicitly says 'Use to find the year label to reconcile, close or lodge', providing clear context for when to use this tool. Lacks explicit exclusions or alternatives but is sufficient given the sibling list.

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