CloudForge 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 only states the action without disclosing behavioral traits like required permissions, whether the cancellation is reversible, rate limits, or what happens after cancellation. 'Cancel' implies a mutation, but no safety or side-effect details are given, leaving significant 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 a single, front-loaded sentence with zero waste—every word contributes directly to explaining the tool's purpose. It's appropriately sized for a simple tool with one parameter and no complex behavior to elaborate.

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 tool's mutation nature (cancel), lack of annotations, and no output schema, the description is incomplete. It doesn't cover permissions, side effects, return values, or error conditions, which are critical for an agent to use this tool correctly in context with siblings like cloudforge_invite_member.

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 the single parameter (invitation_id as UUID). The description adds no additional parameter semantics beyond what's in the schema, but with 0 parameters needing extra explanation, a baseline of 4 is appropriate as no compensation is required.

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 ('Cancel') and resource ('pending organisation invitation by its ID'), distinguishing it from siblings like cloudforge_invite_member (create) and cloudforge_list_invitations (list). It uses precise terminology that directly conveys the tool's function.

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 there's a pending invitation to cancel, but provides no explicit guidance on when to use this versus alternatives like cloudforge_remove_member (for existing members) or prerequisites. It mentions 'pending' which helps differentiate from non-pending states, but lacks explicit when/when-not instructions.

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