Read Multimeter docs

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

Annotations declare readOnlyHint=true, covering the safety profile. The description adds the token-efficiency context ('min' is small) but doesn't describe return format, pagination, or error behavior. Since annotations already establish read-only nature, this is adequate but not exceptional. No contradictions found.

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 efficient, with each sentence earning its place: purpose, defaults, alternatives, and exclusions. It's front-loaded with the core trigger. Slightly long but every clause adds actionable information.

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?

For a read-only documentation lookup with two enums and no output schema, the description covers all necessary context: when to use, parameter nuances, and explicit alternatives. An agent can confidently call this tool without additional clarification.

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% with descriptions for both parameters. The description adds practical guidance beyond the schema: clarifies the 'min' vs 'full' tradeoff and that 'workflow' is the appropriate topic for MCP-first steps. This enriches the semantic understanding beyond mere enum values.

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?

Description clearly states the tool retrieves Multimeter YAML syntax rules, a specific verb+resource. It distinguishes itself from siblings by explicitly naming scaffold_test as the alternative for new API tests and listing forbidden commands. The purpose is unambiguous and differentiated.

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 explicit when-to-use ('Call when you need Multimeter YAML syntax rules'), defaults, when to deviate ('Use pack full only for rare/advanced syntax'), and alternatives ('prefer scaffold_test over loading docs'). Also gives explicit exclusions for testlight, npx, npm, shell, and node commands, leaving no ambiguity about routing.

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