set_form_submission_notification

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

Annotations already provide idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds that it is a per-user toggle, which is consistent with idempotency. It doesn't reveal additional behavioral traits like permissions or side effects, but the combination of annotations and description sufficiently covers the behavior for this simple mutation.

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 sentences, no fluff, front-loaded with the key action and differentiator. Every sentence adds value and is appropriately concise for the tool's simplicity.

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 straightforward toggle tool with 5 parameters and no output schema, the description along with annotations and schema covers the essential information. Missing output description is minor, and the tool's behavior is clear given its simplicity.

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 100% with clear descriptions for all 5 parameters. The tool description does not add extra semantic value beyond what's already in the input schema, so a baseline score of 3 is appropriate.

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?

Description clearly states the action (toggle), the resource (email-on-submit notifications for a specific user on a form view), and distinguishes from sibling set_form_metadata. The verb 'toggle' and resource are specific and 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?

Description explicitly says 'Per-user, not per-form (separate from set_form_metadata)', which tells the agent when to use this tool versus an alternative. While it doesn't exhaustively list all when-not cases, it provides clear context for differentiation among siblings.

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