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 discloses the return format (JSON with nodes, edges, configurations) but doesn't mention authentication needs, rate limits, error handling, or whether it's a read-only operation. For a fetch tool with no annotations, this is adequate but lacks behavioral details.

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 two concise sentences with zero waste: the first states the purpose, and the second specifies the return format. It's front-loaded and appropriately sized for a simple fetch tool.

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 (one parameter, no output schema, no annotations), the description is reasonably complete. It covers purpose and return format, but could improve by adding error cases (e.g., invalid ID) or behavioral context. No output schema exists, so describing returns is valuable.

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 the single parameter 'diagram_id' as a UUID. The description adds no additional meaning beyond what's in the schema, such as format examples or validation rules, meeting the baseline for high coverage.

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 ('Fetch'), the resource ('a saved diagram by ID'), and the return format ('full JSON: nodes, edges, resource configurations'). It distinguishes from siblings like 'cloudforge_list_diagrams' (which lists diagrams) and 'cloudforge_diagram_to_mermaid' (which converts diagrams).

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 a specific diagram ID is known, but doesn't explicitly state when to use this tool versus alternatives like 'cloudforge_list_diagrams' (to find IDs) or 'cloudforge_recent_diagrams' (for recent ones). No exclusions or prerequisites are mentioned.

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