scm-mcp

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states this is an update operation (implying mutation) but doesn't disclose permission requirements, whether changes are reversible, rate limits, error conditions, or what happens to unspecified fields (partial vs. full updates). For a mutation tool with 15 parameters, this is inadequate.

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 well-structured with a clear purpose statement followed by a comprehensive parameter list. Every sentence earns its place, though the parameter section is lengthy (necessary given the parameter count). It could be slightly more front-loaded with critical behavioral information.

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 complexity (15 parameters, mutation operation, no annotations, no output schema), the description is partially complete. It excels at parameter semantics but lacks critical behavioral context for a mutation tool. The absence of output schema means the description should ideally mention what the tool returns, but it doesn't.

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?

With 0% schema description coverage, the description fully compensates by providing clear semantic explanations for all 15 parameters. Each parameter is listed with brief but meaningful context (e.g., 'New action — "allow" or "deny"', 'New source zones', 'Optional TSG ID or named alias'), adding substantial value beyond the bare schema.

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 'Update' and resource 'existing security rule', making the purpose specific and understandable. It distinguishes itself from creation tools (e.g., scm_create_security_rule) by focusing on modification, but doesn't explicitly differentiate from other update tools like scm_update_address or scm_update_nat_rule.

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 rule_id from scm_get_security_rule), when not to use it (e.g., for bulk updates), or how it differs from similar update tools for other resource types in the sibling list.

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