Rebillia MCP Server

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

No annotations are provided, so the description carries full burden. It states the action is a deletion but lacks critical behavioral details: whether deletion is permanent or reversible, permission requirements, side effects (e.g., impact on related records), error conditions, or response format. The HTTP method hint ('DELETE') is minimal and doesn't compensate for these gaps.

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—two brief sentences with zero wasted words. It front-loads the core action and includes a technical hint ('DELETE /invoices/{invoiceId}') that could aid implementation, though this doesn't fully address behavioral transparency.

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 destructive tool with no annotations and no output schema, the description is incomplete. It fails to address key aspects like irreversibility, authorization needs, error handling, or what happens upon success (e.g., confirmation message). Given the complexity of deletion operations, this leaves significant gaps for an AI agent.

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%, with the single parameter 'invoiceId' documented as 'Invoice ID (required)'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or validation rules, so it meets the baseline for high schema coverage without adding value.

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 ('Delete') and resource ('an invoice'), making the purpose immediately understandable. It distinguishes itself from siblings like 'void_invoice' by specifying deletion rather than voiding, though it doesn't explicitly contrast with other deletion tools like 'delete_customer' or 'delete_product'.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., invoice must be in a deletable state), exclusions (e.g., cannot delete paid invoices), or compare with similar tools like 'void_invoice' in the sibling list, leaving the agent to infer usage context.

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