Pocketsmith MCP Server

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

With no annotations, the description carries full burden but only states 'Create a new transaction' without disclosing behavioral traits. It doesn't mention permissions needed, whether creation is irreversible, rate limits, or what happens on success/failure. For a mutation tool with 10 parameters, this is inadequate.

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 extremely concise with just three words, front-loaded and zero waste. Every word earns its place, though it may be overly brief for such a complex tool.

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 creation tool with 10 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the creation process, return values, error handling, or how it fits with sibling tools. The brevity leaves too many gaps given the complexity.

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 the schema fully documents all 10 parameters. The description adds no additional meaning beyond the verb 'create', which is already implied by the tool name. Baseline 3 is appropriate as the schema does all the work.

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 'Create a new transaction' clearly states the action (create) and resource (transaction), but it's vague about scope and doesn't distinguish from sibling tools like pocketsmith_update_transaction or pocketsmith_delete_transaction. It lacks specificity about what kind of transaction or context.

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 this tool vs. alternatives is provided. The description doesn't mention prerequisites, when to choose this over update_transaction, or how it relates to other tools like categorize_transaction. Usage is implied but not explicitly stated.

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