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

With no annotations, the description carries the burden and adds useful context: 'Subject to the same validation and per-IP rate limits as the contact form itself.' This discloses side effects and constraints beyond the schema. It could mention success/failure behavior, but the existence of an output schema reduces that need.

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 a single concise sentence (13 words) with no filler. It front-loads the purpose and adds one key behavioral constraint, making it efficient and easy to parse.

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 simple tool (4 required params, no annotations, and an output schema), the description covers the core purpose and a key behavioral constraint. It lacks explicit alternative guidance and parameter semantics, but these are partly addressed by the schema and obvious sibling differences, making it reasonably 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?

Schema description coverage is 0%, so the description should compensate, but it does not mention any parameters. Although parameter names (name, email, subject, message) are self-explanatory and the schema includes formats, the description adds no additional meaning or guidance on parameter usage.

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 action ('Send Cameron a message') and the resource ('site contact form'), which is a specific verb+resource. It distinguishes itself from sibling tools like get_post or subscribe_newsletter by indicating a direct message submission.

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 implies usage for contacting Cameron through the form but does not explicitly state when to use this tool versus alternatives (e.g., subscribe_newsletter or search tools). It provides context about validation/rate limits but no explicit when-not-to-use guidance.

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