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

No annotations provided. Description only says 'request a session unlock' but does not disclose side effects, synchronization, authentication requirements, or success/failure behavior. Minimal disclosure for a likely mutating operation.

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, front-loaded with key info. No fluff, but could add more context without sacrificing conciseness (e.g., what the unlock entails).

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?

Given no annotations, partial schema coverage, and an output schema not described, the description is incomplete. No explanation of dpop_token or response format. Requires more detail for a complete understanding.

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 has 2 params (npub with description, dpop_token without). Description adds no parameter info; dpop_token remains undocumented. Schema coverage is 50%, and description fails to compensate.

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?

Description clearly states 'Request a session unlock after timeout.' Specifies verb (request), resource (session unlock), and context (after timeout). Distinguishes from siblings like taxsort_check_unlock (check status) and taxsort_create_session (create session).

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 vs alternatives (e.g., taxsort_check_unlock for checking unlock status). No prerequisites mentioned (e.g., need an existing session that is locked).

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