Rebillia MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the HTTP method (GET) and pagination parameters, but doesn't describe important behaviors like whether this is a read-only operation, what authentication is required, rate limits, error conditions, or what the response format looks like (especially critical since there's no output schema).

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 with two sentences that each serve a purpose - the first states the core functionality, the second mentions optional parameters. It's front-loaded with the main purpose and wastes no words, though it could be slightly more 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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the response contains (payment method objects, their structure, fields), error handling, authentication requirements, or how to interpret pagination results. The agent would struggle to use this tool effectively without additional context.

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 already documents all three parameters thoroughly. The description adds minimal value by mentioning 'Optional: pageNo, itemPerPage' but doesn't provide additional context about pagination behavior or parameter interactions beyond what's in the schema descriptions.

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 action ('List all payment methods') and target resource ('for a customer'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_customer_payment_method' (singular vs. plural), though the distinction is somewhat implied by the 'list' vs. 'get' naming convention.

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 like 'get_customer_payment_method' or other customer-related tools. It mentions pagination parameters but doesn't explain when pagination is needed or how to handle large result sets.

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