m3_call

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

No annotations are present, so description carries full burden. It reveals batch isolation, cap of 100, dry_run behavior, and destructive gate requirement. Single-call failure behavior is not detailed, but key behavioral traits are disclosed.

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?

A single paragraph of 5 sentences, front-loaded with main purpose. Each sentence adds distinct value (single call, batch, dry_run, referrals). Could be slightly more structured, but it's concise and efficient.

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?

No output schema exists, so description should clarify return values beyond 'Returns JSON'. Does not specify that single calls return the invoked tool's result, batch returns array, or error format. Lacks detail for a complex meta-tool.

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 description must compensate. It explains tool, args, batch, and dry_run, adding meaning beyond their titles. However, 'database' parameter is not explained, and batch item structure is incompletely specified.

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 it invokes any m3 catalog tool by name without loading its domain, and gives concrete examples (single call, batch, dry_run). It distinguishes itself from siblings like m3_index by referencing it as a prerequisite for learning tool args.

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 clear context for when to use (low-token path) and references m3_index for unknown args. Mentions destructive tool requirement and batch limits. Lacks explicit 'when not to use' but overall direction is strong.

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