Get Fiscal Year

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

Annotations already provide readOnlyHint=true, so description adds value by listing the returned data categories but does not disclose additional behavioral traits (e.g., permissions, limits, side effects). Adequate but not exceptional.

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?

Single sentence captures tool's purpose and return content with no redundancy or unnecessary words. Efficiently front-loaded.

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 simple tool (1 param, no output schema), description reasonably covers return data fields. Could be more complete by noting any error conditions or year validity, but adequate for basic usage.

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 0% with one property 'year' (integer). Description mentions 'by its year' but does not explicitly clarify the parameter's meaning, format, or constraints (e.g., range, required). Adds marginal semantic value beyond schema.

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?

Description clearly states it returns full details of a fiscal year by a specific year, listing explicit fields (result, revenues, expenses, depreciations, VAT, form_data, teletransmission info). This distinguishes it from sibling tools like list_fiscal_years (list) and compute_fiscal_year (compute).

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?

Description implies usage when needing comprehensive details of a single fiscal year, but lacks explicit when-to-use vs when-not-to-use guidance. No mention of alternatives or prerequisites.

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