scm-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a NAT rule, implying a destructive mutation, but does not mention potential consequences (e.g., network impact, irreversibility), required permissions, or error conditions. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 appropriately sized and front-loaded, starting with the core action. The two-sentence structure is efficient, with the first stating the purpose and the second detailing parameters. There is no wasted text, though it could be slightly more structured with bullet points for parameters.

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 complexity (destructive mutation), lack of annotations, and no output schema, the description is incomplete. It fails to address critical aspects like behavioral traits (e.g., confirmation prompts, side effects), error handling, or return values, leaving the agent with insufficient information for safe and effective 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?

Schema description coverage is 0%, so the description must compensate. It explains both parameters: 'rule_id' as 'UUID of the NAT rule to delete' and 'tsg_id' as 'Optional TSG ID or named alias' with a default. This adds meaningful context beyond the schema's basic types, clarifying the purpose and optionality of each parameter effectively.

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 ('Delete a NAT rule') and identifies the resource ('by UUID'), distinguishing it from sibling tools like 'scm_create_nat_rule' and 'scm_get_nat_rule' through the verb 'Delete'. It precisely conveys what the tool does without being vague or tautological.

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, such as 'scm_update_nat_rule' for modifications or 'scm_list_nat_rules' for viewing. It lacks context about prerequisites, like needing an existing NAT rule, and does not mention any exclusions or specific scenarios for its application.

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