Ploi 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 for behavioral disclosure. It mentions 'searching for a domain' which implies a lookup operation, but doesn't clarify if this is a read-only action, whether it modifies files, what permissions are needed, or what happens on failure. For a tool that likely writes configuration files, this lack of detail about mutation behavior and potential side effects is a significant gap.

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 perfectly concise with two sentences that each serve a distinct purpose: the first explains what the tool does, and the second provides usage guidance. There's zero wasted language, and the information is front-loaded with the core functionality stated immediately.

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 has no annotations, no output schema, and 2 parameters with full schema coverage, the description provides adequate basic context about purpose and usage. However, for a tool that likely performs file system operations (creating/modifying .ploi.json), the description should do more to explain behavioral aspects like what happens if the file already exists, whether changes are reversible, or what the expected output looks like.

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 both parameters ('project_path' and 'domain') well-documented in the schema. The description adds minimal value beyond the schema by mentioning 'searching for a domain' which relates to the 'domain' parameter, but doesn't provide additional syntax, format, or usage details. This meets the baseline score of 3 when schema coverage is high.

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 ('Initialize .ploi.json config') and resource ('for a project'), specifying it's done by searching for a domain. It distinguishes from siblings like 'deploy_project' or 'get_site' by focusing on configuration initialization rather than deployment or retrieval operations. However, it doesn't explicitly differentiate from all siblings, such as 'find_site_by_domain' which also involves domain searching.

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 provides explicit guidance on when to use this tool: 'Use when user wants to link a project to a Ploi site.' This gives clear context about the intended scenario. However, it doesn't specify when NOT to use it or mention alternatives like 'find_site_by_domain' for domain lookup without configuration, leaving some room for improvement in sibling differentiation.

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