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

No annotations are provided, but the description discloses dev-only scope, fake-canary requirement, transient operation, and minimal return value (delivery status). It omits auth requirements, rate limits, or side effects, but for a test-only transport proof it covers the critical safety and behavior constraints.

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?

Three brief sentences, each front-loaded: what it is, what it does, and the safety warning. No filler or repetition.

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 simple one-parameter dev tool with no output schema, the description covers output ('only delivery status') and safety. However, it does not compensate for the fully undocumented input parameter or describe possible transport side effects, so it is adequate but not fully complete.

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?

The schema provides only a title for the single required 'canary' string and 0% description coverage. The description clarifies that the value must be a fake canary rather than a real credential, which adds some meaning, but it gives no format, length, or example, leaving the parameter largely unspecified.

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?

Names a specific action (forward a fake canary) and states its purpose (dev-only transport proof) plus output scope (delivery status). The sibling tools are all search/fetch utilities, so the dev-only testing niche is easy to distinguish, though 'canary' remains domain jargon.

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?

Explicitly limits use to dev-only transport proof and warns never to use a real credential, giving a clear context and exclusion. It does not name alternative tools, but none of the search/fetch siblings overlap.

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