m3_help_capabilities

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. However, it does not state whether the tool is read-only, has side effects, or requires any permissions. The term 'Discover' likely implies a safe introspection call, but this is not explicitly confirmed, leaving uncertainty for the agent.

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 concise: two sentences with no redundant information. The first sentence quickly establishes what the tool does, and the second adds relevant filtering options. Every word contributes to understanding.

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?

Given the lack of output schema and annotations, the description should explain the return format or behavioral details. It mentions 'capabilities, parameters, and availability' as output but does not describe structure or how to interpret results. This under specification may confuse the 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?

The input schema has 0% description coverage, so the description must add meaning. It mentions filtering by domain and searching by keywords, which maps to the 'domain' and 'query' parameters, but provides no details on 'timeout' or 'database'. This partial coverage is adequate but not complete.

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 the tool's purpose: 'Discover m3-memory tool capabilities, parameters, and availability.' The verb 'Discover' is specific, and the resource 'tool capabilities, parameters, and availability' is well-defined. This distinguishes it from sibling tools like memory_search or agent_list, which focus on actual data rather than tool introspection.

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 implies usage context by mentioning filtering by domain or searching by keywords, but it does not explicitly state when to use this tool versus alternatives like tools_list_domains or tools_load_domain. No when-not guidance or explicit alternative comparisons are provided.

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