Pocketsmith MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists category rules, implying a read-only operation, but doesn't disclose details like whether it returns all rules at once, supports pagination, requires authentication, or has rate limits. For a tool with zero annotation coverage, this is a significant gap in behavioral context.

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, efficient sentence that front-loads the core action ('List all category rules') and adds clarifying context ('automatic categorization rules') without unnecessary words. Every part earns its place, making it highly concise and well-structured.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose but lacks usage guidelines and behavioral details like response format or pagination. For a list operation, this is minimally viable but could be more complete by addressing how results are returned.

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 input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter information, which is acceptable given the lack of parameters. Baseline score is 4 for 0 parameters, as there's nothing to compensate for, and the description doesn't introduce confusion.

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 ('all category rules') with additional clarifying context ('automatic categorization rules'). It distinguishes this tool from siblings like 'pocketsmith_list_cudget' or 'pocketsmith_list_transactions' by specifying the type of rules. However, it doesn't explicitly differentiate from 'pocketsmith_create_category_rule' in terms of operation type, though the verb 'List' implies read-only versus creation.

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. It doesn't mention prerequisites, such as needing existing category rules to list, or compare it to siblings like 'pocketsmith_list_categories' or 'pocketsmith_list_transactions' for related data. Usage is implied by the action 'List all', but no explicit context or exclusions are provided.

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