Sync Tax Codes

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool 'returns the modified object' and includes API category/endpoint. It does not disclose idempotency, error handling, or permissions beyond the annotations. The description adds some value but not substantial behavioral detail.

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 a few sentences. Some redundancy exists (e.g., 'creates or updates a batch' followed by 'Use this to update'). It includes useful but non-essential API metadata. Overall, it is well-structured and front-loaded with key information.

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's simplicity (2 parameters, no output schema), the description covers purpose, usage, and return value. It lacks details on batch size limits, error handling, or idempotency, but for a straightforward sync tool, it provides sufficient 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?

Schema coverage is 100%, so the schema already documents company_id and updates. The description merely repeats 'Required parameters: company_id, updates' and provides a high-level endpoint reference. It does not elaborate on the structure of 'updates' array, which is generically typed as {} in the schema. Thus, it adds minimal meaning beyond the 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?

The description clearly states it creates or updates a batch of Tax Codes, specifying the verb (sync) and resource (tax codes). It distinguishes from individual create/update tools (e.g., create_tax_code) by emphasizing batch operation. The mention of 'only the supplied fields are changed' clarifies partial updates.

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 explicitly says 'Use this to update an existing Tax records', implying batch updates. It provides context for when to use the tool but does not contrast with individual create/update tools or specify when not to use it. Still, it gives clear direction for batch scenarios.

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