PEX MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read operation, the description confirms nothing about safety, side effects, rate limits, or what determines which transfer details are returned given zero input 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?

Though brief, this represents under-specification rather than true conciseness. The single sentence fails to earn its place by providing no actionable information beyond the function name, wasting the opportunity to add critical context.

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 zero-parameter getter with no output schema and no annotations, the description is insufficient. It does not clarify what business context is required, what scope of transfers are retrieved (all? current? pending?), or how the returned data is structured.

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?

Input schema contains zero parameters (100% coverage of empty set). Per calibration rules, 0 params warrants a baseline score of 4. No parameter semantics are required in the description.

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 'Get business one-time transfer details' is tautological, merely restating the tool name with slight expansion. It fails to specify what constitutes a 'one-time transfer' in this context or how it differs from sibling tools like pex_get_payment_transfer.

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 provided on when to use this tool versus alternatives (e.g., pex_get_payment_transfer), nor any prerequisites or conditions for invocation. The user has no criteria for selecting this tool.

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