Send notification

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

The description discloses zero behavioral traits. Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, and the description adds nothing about side effects, delivery guarantees, whether sending is async or blocking, rate limits, or what the returned output schema contains. There is no contradiction, but the description is entirely vacuous on behavior.

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?

At three words, the description is short, but this is under-specification, not conciseness. There is no front-loaded value; the entire description merely echoes the tool name. A genuinely concise description would still convey purpose and scope in a sentence or two.

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?

The tool is relatively simple (2 params, 100% schema coverage, output schema present), which lowers the bar somewhat. But the description provides no context about what a notification is, who receives it, delivery mechanics, or side effects. For a tool that mutates state (readOnlyHint=false), the absence of any behavioral context leaves the agent guessing.

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 100%, so both parameters (subject and body) are documented in the input schema with titles and descriptions. Per the calibration baseline, the description need not re-explain them, and it doesn't. However, it also adds no operational meaning beyond the schema – e.g., format constraints, whether subject maps to a display header, or body length semantics beyond maxLength.

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 'Send notification' is a pure tautology – it restates the tool name and title with zero additional information. It does not specify the delivery channel, recipient, medium (email, push, SMS), or how this tool differs from its 30+ siblings. An agent gets nothing beyond the name itself.

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?

No guidance exists about when to use this tool versus any alternative. None of the sibling tools are mentioned, and there is no context about prerequisites (e.g., whether a user must be logged in, whether a notification service must be configured) or situations where this tool would or would not be appropriate.

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