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 this is a read operation ('Get'), which implies it's non-destructive, but doesn't clarify authentication needs, rate limits, error responses, or what the return data includes (e.g., rule details in JSON). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loaded with the core purpose in the first sentence, followed by parameter details in a structured 'Args:' section. It's efficient with minimal waste, though the parameter explanations could be slightly more detailed (e.g., clarifying UUID format). No extraneous information is included.

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 no annotations, no output schema, and 0% schema description coverage, the description provides basic purpose and parameter semantics but lacks behavioral context (e.g., error handling, return format) and usage guidelines. It's adequate for a simple read tool but incomplete for full agent understanding, especially without output details.

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' and 'tsg_id' as 'Optional TSG ID or named alias' with a default value. This adds crucial meaning beyond the bare schema (which only shows types and titles), though it doesn't detail UUID format or TSG alias examples. For 2 parameters, this is strong but not exhaustive.

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 ('Get a single NAT rule') and resource ('by UUID'), distinguishing it from sibling tools like 'scm_list_nat_rules' (which lists multiple) and 'scm_create_nat_rule'/'scm_update_nat_rule'/'scm_delete_nat_rule' (which modify rather than retrieve). The verb 'Get' is precise and unambiguous.

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?

No explicit guidance is provided on when to use this tool versus alternatives. While the purpose implies it's for retrieving a specific NAT rule, there's no mention of prerequisites (e.g., needing the rule's UUID), comparison to 'scm_list_nat_rules' for browsing, or error conditions (e.g., what happens if the rule doesn't exist). The description assumes context without stating it.

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