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

No annotations provided. Description mentions the matching and writing behavior but does not disclose side effects (e.g., overwriting existing rules), authentication requirements (e.g., npub), or output format. Partially transparent but incomplete.

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?

Two concise sentences, no redundancy. All critical information about the rule creation is front-loaded, with no wasted words.

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?

Covers core functionality but lacks context on authentication (npub required for billing) and error handling. Output schema exists but description doesn't reference it. Adequate but with gaps for a 9-parameter tool.

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 only 11% (only npub described). The description adds meaning to key parameters (description_pattern as regex, amount_operator values, new_description as optional rewrite) but omits details for npub, dpop_token, session_id, etc. Moderate value added.

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 'Create a classification rule' with a specific verb and resource. It distinguishes from siblings like taxsort_apply_rules, taxsort_delete_rule, and taxsort_get_rules by focusing on creation.

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?

No guidance on when to use this tool versus alternatives (e.g., taxsort_apply_rules for applying rules). The description only explains what the tool does, not when it should be chosen.

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