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

Describes the destructive action of deleting all transactions and classifications. With no annotations, the description carries full burden; it lacks details on irreversibility, authentication needs, or side effects.

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?

Single sentence of 15 words, front-loaded with the core action and purpose. Every word is relevant and concise.

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?

Lacks details on prerequisites (e.g., valid session), return values (despite output schema existing), and fails to describe two parameters. For a destructive tool with no annotations, this is insufficient.

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?

Description does not explain any of the three parameters. Schema description coverage is only 33% (npub has description), leaving two parameters (dpop_token, session_id) undocumented in both schema and 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?

Clearly states 'Delete all transactions and classifications for a session', specifying the verb and resource. Distinguishes from siblings like taxsort_delete_account_transactions and taxsort_delete_classification by targeting all session data.

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?

Explicitly mentions the use case 'so CSVs can be re-imported', guiding the agent on when to use this tool. Does not explicitly state when not to use or list alternatives, but context is clear.

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