m3_help_capabilities

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

No annotations are provided, so the description carries the full burden. It states the tool discovers capabilities and parameters, implying read-only behavior. However, it does not explicitly confirm safety (e.g., no side effects) or disclose any other behavioral traits.

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 two sentences: the first states the purpose, and the second lists filtering options. It is front-loaded and concise with no redundant words, earning its place.

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 help/discovery tool with three optional parameters and no output schema, the description covers the primary purpose and filtering options. It does not describe the output format, but given the tool's nature, it is still adequately informative.

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 0%, so the description must add meaning. It explains 'domain' and 'query' parameters but does not mention the 'database' parameter. This partial addition raises the score slightly above baseline, but a complete explanation would have been better.

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 uses a specific verb ('Discover') and clearly identifies the resource ('m3-memory tool capabilities, parameters, and availability'). It distinguishes from siblings by mentioning filtering by domain or keywords, which helps the agent understand when to use this tool.

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 explicitly states the tool allows filtering by logical domain or keyword search, giving clear context for when to use it. However, it does not explicitly mention when not to use it or alternatives, though sibling tools like tools_load_domain are distinct.

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