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

No annotations are provided, so the description carries full burden. 'Get' implies a read operation, but the description does not clarify any behavioral traits such as read-only status, side effects, authentication requirements, or what happens if no rules exist. The agent is left to assume safe behavior without confirmation.

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 a single, front-loaded sentence with no unnecessary words. Every word is essential: verb, resource, scope. It is perfectly concise for a simple retrieval tool.

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?

Although an output schema exists (so return format is covered), the description lacks essential context: what constitutes a 'classification rule', how the 'current patron' is identified, and how this tool relates to other rule-related tools. Given the tool complexity and sibling count, the description is incomplete for safe agent 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 description coverage is only 33% (only npub has a description). The tool description adds no meaning to any of the three parameters—it does not explain npub, dpop_token, or session_id or how they affect results. An agent must rely solely on the schema, which has sparse descriptions and defaults.

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 uses a specific verb ('Get') and clearly identifies the resource ('all classification rules') with a scope ('for the current patron'). It distinguishes this tool from siblings like taxsort_save_rule, taxsort_delete_rule, and taxsort_apply_rules, which involve modifying or applying rules instead of just retrieving them.

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 provides no guidance on when to use this tool versus alternatives. Given 79 sibling tools, many of which also operate on rules (e.g., taxsort_count_rule_matches, taxsort_get_custom_categories), an agent would not know when retrieval is appropriate or what prerequisites exist. No when-not-to-use or alternative tool mentions.

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