CloudForge 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 this is a list operation, implying read-only behavior, but doesn't disclose critical details like whether it requires admin permissions, how results are paginated or sorted, or if there are rate limits. For a tool with zero annotation coverage, this leaves significant behavioral 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, efficient sentence that front-loads the core action ('List all pending organisation invitations') and appends relevant output details. There is no wasted text, and it directly communicates essential information without redundancy.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers what the tool does and what data it returns, but lacks context on permissions, pagination, or error handling. Without annotations or output schema, more behavioral detail would improve completeness for a list operation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing instead on the tool's purpose and output attributes. This meets the baseline for zero-parameter tools.

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 verb ('List') and resource ('pending organisation invitations') with specific attributes enumerated (email, name, role, sent date, expiry). It distinguishes from siblings like 'cloudforge_list_members' by focusing on pending invitations rather than current members. However, it doesn't explicitly contrast with 'cloudforge_invite_member' for creation vs. listing.

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 context by specifying 'pending' invitations, suggesting this tool is for reviewing outstanding invites rather than active members or historical data. However, it lacks explicit guidance on when to use this versus 'cloudforge_list_members' or 'cloudforge_cancel_invitation', and doesn't mention prerequisites like authentication or access rights.

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