MCP cldkctl Server

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

With no annotations provided, the description carries full responsibility for behavioral disclosure but offers none. It doesn't indicate whether this is a read or write operation (likely a write given 'add'), what permissions are required, whether it sends invitations or directly adds members, potential side effects, or error conditions. The description is completely silent on behavioral traits beyond the minimal implication of an endpoint call.

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?

While the description is brief (one sentence), it's under-specified rather than concise. The single sentence 'Call the cldkctl_org_member_add endpoint' wastes its opportunity to convey meaningful information, essentially repeating the tool name. True conciseness would efficiently communicate purpose and context, which this description fails to do.

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?

For a tool that appears to perform a write operation (adding organization members) with no annotations and no output schema, the description is completely inadequate. It doesn't explain what the tool does, when to use it, what behavior to expect, or what results are returned. Given the complexity implied by the sibling tools and the lack of structured metadata, the description fails to provide the necessary context for effective tool use.

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 schema description coverage is 100%, with all three parameters (user_id, role_id, project_id) clearly documented in the input schema. The description adds no additional parameter information beyond what the schema provides. According to the scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter details in the description.

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 'Call the cldkctl_org_member_add endpoint' is a tautology that merely restates the tool name in different words. It doesn't specify what the tool actually does (adds a member to an organization), what resource it operates on, or how it differs from sibling tools like cldkctl_org_member_activate or cldkctl_org_member_delete. The name suggests adding an organization member, but the description fails to clarify this purpose.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing admin permissions), when it's appropriate (e.g., for new members vs. existing ones), or how it relates to sibling tools like cldkctl_org_member_edit or cldkctl_org_member_delete. Without any usage context, an agent cannot make informed decisions about tool selection.

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