scm-mcp

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

No annotations are provided, so the description carries the full burden. It states the tool updates a rule, implying mutation, but doesn't disclose behavioral traits such as required permissions, whether changes are reversible, error handling, or rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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: the first sentence states the purpose, followed by a structured list of parameters. Each parameter entry is brief and relevant, with no wasted sentences. Minor improvements could include grouping related parameters for better readability.

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 (12 parameters, mutation tool), lack of annotations, and no output schema, the description is incomplete. It covers parameters but misses critical context: behavioral transparency, usage guidelines, and output details. For a tool with this many parameters and no structured support, more comprehensive guidance is needed.

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 description lists all 12 parameters with brief explanations (e.g., 'New name (optional)'), adding meaning beyond the input schema, which has 0% description coverage. It clarifies optionality and provides a default for 'tsg_id'. However, it doesn't explain parameter interactions or constraints, leaving some semantic gaps.

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 tool's purpose: 'Update an existing PBF rule.' It specifies the verb ('Update') and resource ('PBF rule'), making the action explicit. However, it doesn't distinguish this from sibling tools like 'scm_update_nat_rule' or 'scm_update_security_rule' beyond the resource name, missing explicit differentiation.

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 lacks context about prerequisites (e.g., rule existence), exclusions, or comparisons to sibling tools like 'scm_create_pbf_rule' or 'scm_delete_pbf_rule'. The agent must infer usage from the tool name alone.

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