get_tax

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

The description adds no behavioral context beyond what annotations already provide. Annotations state readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is known. However, there is no extra disclosure about return format, error behavior, or the fact that it operates on a specific tax_id.

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 extremely short ('Fetch a tax') and wastes no words, but it is under-specified. It conveys the basic action but lacks necessary detail like 'by ID', making it borderline between concise and incomplete.

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 the tool has only one parameter and no output schema, the description is minimal but still leaves gaps. It does not explain what a 'tax' represents in the domain, what fields are returned, or how this relates to list_taxes. The annotations and schema do not compensate for this lack of context.

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 input schema covers 100% of parameter semantics: tax_id is required and described as 'the id of the tax'. The description adds nothing about the parameter, so with high schema coverage, the baseline score of 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?

The description uses a specific verb 'Fetch' and identifies the resource 'a tax', which clearly indicates retrieving a single tax object. It is distinct from sibling tools like list_taxes (plural) and delete_tax (destructive), though it does not explicitly mention retrieval by ID.

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 description gives no guidance on when to use this tool vs alternatives. It does not mention that this is for fetching a single tax by ID and that list_taxes should be used for multiple taxes, nor does it provide any context about prerequisites or exclusions.

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