create_rule

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

Adds rich behavioral context beyond annotations: persistence across MCP downtime, non-retroactivity, AND logic for multiple conditions, comma-separated values, stop_processing default, and to_trash not being permanent deletion. This complements the annotations (readOnly=false, idempotent=false, destructive=false) with meaningful detail.

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 well-structured: starts with core purpose, followed by key behavioral notes, then a clean bullet-style Args list. Every sentence adds value, and repetitive clarifications ('カンマ区切りで複数可') are necessary for each relevant parameter. It is appropriately sized for a 10-parameter tool with important nuances.

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 complexity (10 params, 0% schema coverage), the description is remarkably complete: it covers purpose, persistence, scope of application, condition semantics, and parameter meanings. An output schema exists, so return values need not be described. No critical operational details are missing.

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%, but the description explains every parameter with practical guidance. For example, 'name' is described as a self-explanatory label, 'to_trash' clarifies it's not permanent deletion, 'stop_processing' explains its default behavior, and 'sequence' explains the default append behavior. This fully compensates for the schema's lack of descriptions.

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 function: '受信トレイに自動振分ルールを作る' (creates an automatic routing rule in the Inbox). It also specifies scope (applies to future emails, not retroactive) and explicitly differentiates from sibling 'move_by_search', making the purpose unambiguous.

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?

It provides explicit when-to-use context: rules persist on Outlook side and work even if MCP isn't running. It also states when not to use it: '既に届いているメールには遡って適用されない(それは move_by_search の仕事)' directly naming the alternative tool for retroactive moves.

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