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

Beyond the readOnlyHint:false annotation, the description discloses critical behaviors: credits are escrowed (not spent), not taxable, not counted toward lifetime spending, surplus is refunded weekly, and the pool covers taxes before the wallet is touched. This significantly exceeds annotation coverage.

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 longer than average but every sentence adds value: purpose, mechanism, timing, refund, and parameter guidance. It is front-loaded with the main action and uses parentheses for supplementary details without becoming disorganized.

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?

For a simple two-parameter mutation tool with no output schema, the description is thorough. It explains the full lifecycle (prepay, coverage on tax day, surplus refund) and references the related tool for balance checks. Minor gaps include not specifying behavior when wallet has insufficient credits or when exactly tax day occurs, but these are likely contextual.

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 schema already provides 100% coverage for both parameters. The description adds extra meaning for amount (escrowed, not spent, not taxable, not counted toward lifetime spending), which enriches understanding beyond the schema's basic description.

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 opens with a specific verb and resource: 'Prepay credits toward your next tax assessment.' It clearly distinguishes itself from related tools like get_tax_estimate (which reads) and faction_prepay_tax (which is faction-specific) by focusing on personal wallet-to-tax-pool movement.

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 context on when to use the tool (to avoid being caught short on tax day) and explicitly points to get_tax_estimate for checking obligation and prepaid balance. However, it does not state when not to use it or name direct alternatives beyond the complementary get_tax_estimate.

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