Pocketsmith MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral information. It doesn't disclose whether this is a read-only operation, pagination behavior, rate limits, authentication requirements, or what format/scope of data is returned. 'List' implies reading, but no safety or operational details are provided for a tool with 7 parameters.

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 appropriately concise - a single sentence that states the core purpose. However, it could be more front-loaded with critical information about when to use this versus other transaction listing tools, given the multiple similar siblings.

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?

For a tool with 7 parameters, no annotations, no output schema, and multiple similar sibling tools, the description is inadequate. It doesn't explain return values, pagination, error conditions, or differentiation from alternatives like 'list_transactions' or 'search_transactions'. The agent would struggle to use this tool effectively without trial and error.

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 100%, so all parameters are documented in the schema. The description adds minimal value beyond the schema - it mentions 'optional filters' which aligns with the schema's optional parameters, but doesn't provide additional context about filter combinations, precedence, or practical usage examples.

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 the verb ('List') and resource ('transactions for a specific account') with optional filters. It distinguishes from general 'list_transactions' by specifying account-specific filtering, but doesn't explicitly differentiate from 'list_transaction_accounts' or 'list_transactions_by_category' which are similar sibling tools.

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 minimal guidance - it mentions 'optional filters' but doesn't specify when to use this tool versus alternatives like 'list_transactions' (general listing), 'list_transactions_by_category', or 'search_transactions'. No context about prerequisites, performance considerations, or limitations is provided.

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