test_notification

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

Discloses rate limiting, test flag in audit, and end-to-end pipeline verification. No annotations exist, so description carries full burden; it covers key behavioral traits adequately.

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 that efficiently convey purpose, constraints, and verification scope without wasted words.

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?

Covers key aspects for a test tool (purpose, rate limit, test flag). Missing explicit return value description, but overall adequate given tool simplicity and sibling context.

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 descriptions cover both parameters with 100% clarity. Description adds no extra parameter details beyond schema, so baseline 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 it triggers a test notification with an audit mark, distinguishes from regular notifications, and adds context about rate limiting and end-to-end testing.

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 usage context (rate-limited per wallet at 1/min), but does not explicitly state when to avoid or mention alternative tools like create_notification_rule or list_notifications.

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