create_notification

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

No annotations are provided, so the description must fully disclose behavior. It mentions generating a notification record, HTML template, plain text fallback, and checklist, but does not address side effects, idempotency, permissions, or what happens on errors. The 'best practice checklist' is ambiguous.

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 moderately concise with three clear sections: purpose, recipient types, and generated outputs. The bullet-like lists are efficient, though they lack markdown formatting.

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 tool has 12 parameters and no output schema or annotations, the description is incomplete. It fails to describe the return value, error handling, prerequisites, or what happens to existing notifications. The 'best practice checklist' is vague.

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 50%; the description adds value by explaining recipient types (field, group, role, user) and the generated outputs. However, many parameters like category, reply_to, and email_script are not enriched beyond schema descriptions. Compensates partially.

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 creates a ServiceNow email notification with specific components (HTML template, recipients, conditions). It distinguishes from siblings like create_push_notification by specifying 'email notification'.

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 explains recipient types but does not provide explicit guidance on when to use this tool versus alternatives like create_push_notification or other notification tools. No when-not or comparison with siblings.

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