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

With no annotations, the description must disclose all behavioral traits. It explains the internal sorting/grouping logic (group_sort, sort_col, sort_dir, group_by interaction) which is valuable. However, it omits details about pagination behavior, rate limits, side effects, or the fact that npub is used for credit billing (only in schema's parameter description for npub). The description adds moderate transparency beyond the schema but is not comprehensive.

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 very concise with only 3 sentences. The first sentence provides a high-level summary, followed by specific details on sorting/grouping. No unnecessary words; each sentence adds value. It is well front-loaded.

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 the tool's complexity (16 parameters, output schema exists), the description is incomplete. It fails to explain pagination mechanics, filtering parameters, billing (npub), and many other options. While the output schema may cover return structure, the description should at least cross-reference key parameters. A user would struggle to use this tool correctly without additional documentation.

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 description coverage is only 6% (only npub has a description). The description adds meaning for only 3 parameters (group_sort, sort_col, sort_dir) out of 16, neglecting many important ones like page, page_size, search, filters, etc. Given the low schema coverage, the description should have explained more parameters to aid correct usage.

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 'Server-side filtered, grouped, sorted, paginated transactions', which defines the core purpose. However, it does not distinguish this tool from the sibling 'taxsort_get_transactions', which likely provides simpler transaction retrieval. The explanation of sorting/grouping behavior adds clarity but misses a direct contrast.

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 explicit guidelines on when to use this tool versus alternatives like 'taxsort_get_transactions'. The description assumes the user knows when pagination or grouping is needed, providing no situational context or prerequisites beyond the required session_id.

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