mmp_search

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

The description adds a critical safety warning about not trusting MMP file content, which goes beyond what annotations (none provided) would convey. However, it does not disclose other behavioral traits like permissions or rate limits.

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?

Two concise sentences: first states purpose, second provides critical safety context. No wasted words; front-loaded and scannable.

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 description covers purpose and safety but lacks parameter explanations and usage context. Given the existence of an output schema, return values are covered, but parameter ambiguity and lack of sibling differentiation reduce completeness.

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 0%, yet the description provides no explanation for parameters (file, query, k). This forces the agent to infer semantics from names alone, which is insufficient.

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 'Search index metadata; returns candidates without body text', which specifies the verb (search), resource (index metadata), and distinguishes from siblings that likely return body text (e.g., mmp_read).

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?

No explicit guidance on when to use this tool versus alternatives like mmp_read or mmp_list. The description only implies a search use case but does not provide when-to-use or when-not-to-use criteria.

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