Manage Custom Tax Rule

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'Add or toggle,' implying mutation without explaining consequences, permissions, reversibility, or how the rule is applied to tax calculations. It lacks critical safety and side-effect information expected for a mutation tool.

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, front-loaded, and every sentence earns its place. It quickly states the core function, defines the domain, and provides two illustrative examples without unnecessary verbosity.

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?

The description provides a solid definition and examples, but the tool has 8 parameters and no output schema or annotations. It lacks details on the rule lifecycle (e.g., updating or deleting rules), how 'toggle' maps to enable/disable, and what happens after a rule is added. This is adequate but leaves notable gaps.

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 each parameter has a description in the schema. The tool description adds examples of custom rules but does not elaborate on the specific parameters or their relationships, relying on the schema's minimal definitions. It meets the baseline but adds little extra meaning.

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's function with a specific verb and resource: 'Add or toggle a custom tax rule.' It explains what custom rules are and provides examples, distinguishing it from standard-knowledge tools and calculation tools among the siblings.

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 clear context for when to use the tool: for interpretations, special scenarios, or business-specific policies not in the standard knowledge base. Examples illustrate applicability, though it doesn't explicitly name alternative tools or state when NOT to use it.

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