Cresium MCP Server

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions signer notification and auto-confirmation on approval, but does not disclose permissions required, rate limits, whether the request is reversible, error conditions, or what happens if approval fails. For a tool that initiates a signature process, this is a significant gap in transparency.

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 concise with two sentences that efficiently cover the core action and outcome. It is front-loaded with the main purpose, though it could be slightly more structured by explicitly separating behavioral details. No wasted words, but minor room for improvement in clarity.

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 complexity of creating a signature request with no annotations and no output schema, the description is incomplete. It lacks details on permissions, error handling, response format, and prerequisites, leaving gaps for an AI agent to understand full usage. More context is needed for adequate completeness.

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 description adds minimal meaning beyond the input schema, which has 100% coverage. It mentions the parameter types ('transaction, bulk, or payroll') aligning with the enum in the schema, but does not explain the semantics of the 'id' parameter or provide additional context like format examples or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

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 specific action ('Create a signature request') and the target resources ('for a transaction, bulk, or payroll'), distinguishing it from sibling tools like confirm_transaction or create_invoices. It specifies the purpose as initiating a signing process rather than confirming or creating other entities.

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 implies usage when needing signatures for specific entity types (transaction, bulk, payroll) but does not explicitly state when to use this tool versus alternatives like confirm_transaction or when not to use it. It mentions signers will be notified and approval happens via Dashboard, providing some context but no explicit guidance on tool selection.

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