Au Financial Year

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

No annotations are provided, so the description carries the burden, and it does disclose the governing rule (fiscal year runs 1 July–30 June), which is the essential behavioral fact for interpreting results. It is a pure deterministic mapping with no side effects, auth needs, or rate limits to disclose, though it does not address boundary-date behavior explicitly.

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 sentences, zero waste, with the core semantic definition front-loaded before the usage instruction. Nothing is padded or redundant.

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?

For a one-parameter deterministic conversion with a full input schema and an output schema, the description supplies the one piece of semantics the schemas cannot encode — the definition of the Australian financial year. 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 description coverage is 100% and the single 'date' parameter already documents its YYYY-MM-DD format in the schema. The description adds nothing parameter-specific, so the baseline 3 applies.

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 and resource ('Map a date to the Australian financial year') and immediately defines the domain concept by its boundaries (1 July to 30 June). An agent knows exactly what transformation this performs without opening the schema, and no sibling competes for this function.

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 this whenever a question involves an Australian financial year, rather than assuming a calendar year' — a clear trigger condition plus a caution against the default calendar-year assumption. It stops short of naming alternatives, but no sibling tool is a real substitute for this conversion.

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