mcp_config_auditor__scan_inventory

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

With no annotations, the description carries the full burden; it usefully discloses that no network connection to the audited servers occurs, which is real behavioral context. It says nothing about read-only guarantees, cost, or what a shadowing finding looks like, leaving notable gaps for a scanner with no output schema.

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?

Three short sentences, front-loaded with the outcome, then input instruction, then the key non-behavioral caveat. No filler.

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?

The single input parameter is fully covered, but with no output schema the description never indicates what the scan returns (findings shape, per-server pairing, severity). For a detection tool that is a meaningful omission.

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 coverage is 100% and includes a concrete JSON exemplar, so the parameter is already documented. The description reinforces intent (names and descriptions from each installed server) but adds no format or constraint detail beyond the 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?

States a specific verb+object ("Detect cross-server tool shadowing") and a specific input ("inventory of tool catalogs"), which is far more informative than the generic scan_* siblings. It does not name the closest siblings (discover_shadow_mcp, toxic_flow_auditor__audit_catalog), so the agent must infer the split itself.

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?

"Pass the tool names and descriptions already collected" implies the precondition (inventory pre-collected) and "does not connect to those servers" implicitly excludes live-discovery tools. No explicit when-not or named alternative is given, so the choice between this and discover_shadow_mcp is left to inference.

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