Show Tax Type

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. The description adds that it returns a JSON object and notes required parameters, but does not provide additional behavioral context beyond annotations, such as pagination behavior or rate limits.

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 concise with four focused sentences: purpose, usage, return/required, and API reference. No redundancy, and every sentence adds value within a compact structure.

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?

Despite being a simple show tool, the input schema includes optional pagination params (page, per_page) that are unexplained and potentially misleading for a single-record fetch. The description does not clarify their relevance, which could cause incorrect use.

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 100%, so baseline is 3. The description repeats required parameters (id, company_id) already in schema, but adds no new semantic meaning or formatting rules. The endpoint path clarification is helpful but minimally additive.

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 clearly states the tool shows detailed information for a specific Tax Type by identifier. It uses a specific verb ('show') and resource ('Tax Type'), and distinguishes from siblings like list_tax_types, create_tax_type, etc., by focusing on fetching full details for a single record.

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 says 'Use this to fetch the full details of a specific Tax records by its identifier,' providing clear context for when to use. However, it does not explicitly exclude alternatives or mention when not to use, leaving inference to the agent based on sibling names.

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