query-sop

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

No annotations are provided, and the description solely states 'Query standard operating procedures' without disclosing behavioral traits like read-only nature, rate limits, or authentication needs. The agent cannot infer safety or constraints from this minimal text.

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 a single concise sentence that directly states the tool's purpose. It is front-loaded and contains no wasted words, but is perhaps overly brief.

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?

With no output schema and no annotations, the description fails to explain return format, behavior of the 'detailed' parameter, or what constitutes an SOP. The tool is not fully actionable for an agent.

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 100%, so the input schema fully documents parameters. The description adds no extra meaning beyond the schema, meeting the baseline for adequate parameter semantics.

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 states 'Query standard operating procedures for common MCP operations', which clearly indicates the tool's purpose as retrieving SOPs for operations. However, it does not explicitly distinguish from sibling tools like 'list-sops' or 'get-service-sop', which may cause confusion.

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. Given the siblings include 'list-sops' and 'get-service-sop', explicit usage context is missing, leaving the agent to guess.

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