test_notification

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

Discloses that it triggers a real test notification (with is_test flag) and mentions rate limiting. Absence of annotations is compensated by describing the test nature and pipeline verification, though side effects like audit row creation are implied but not explicit.

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 concise sentences with no wasted words. Purpose is front-loaded followed by key usage details.

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 parameterless test tool with no output schema, the description covers functionality, test nature, rate limit, and pipeline verification. Missing return value info, but not critical.

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?

Input schema has no parameters, so schema coverage is 100%. The description doesn't need to add parameter info; baseline for 0 params is 4.

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 triggers a real test notification with an is_test flag, distinguishing it from other notification tools like list_notifications. The verb 'Trigger' and resource 'test notification' are specific.

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 use: rate-limited per wallet at 1/min and verifies the full pipeline end-to-end, implying it's for testing. No explicit when-not-to-use, but the purpose is well-understood.

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