SidClaw GovernanceMCPServer

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

Discloses key behavioral traits not in annotations: tamper-evident audit trails, human-in-the-loop approval, and policy evaluation requirements.

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?

Well-structured with three purposeful sentences: purpose, configuration, and documentation link; appropriately concise.

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?

Adequately covers the tool's proxy nature, required environment variables, and setup documentation given the simple input schema and lack of output schema.

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 has 100% coverage of the single placeholder parameter; description adds no additional parameter semantics but meets baseline.

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?

Clearly states it wraps upstream MCP servers with specific governance functions (policy evaluation, human-in-the-loop, audit trails), using specific verbs and resources.

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?

Provides configuration requirements and notes it's a placeholder without upstream setup, but lacks explicit decision criteria for when to select this tool vs. alternatives.

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