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

Goes well beyond the annotations by disclosing that it is a two-phase stage-then-confirm operation, that it returns a preview plus action_id, that nothing is sent until confirmed, the 10-listing cap, that it appears on the client's timeline, and that a linked PropertyList account is required so an agency API key alone is insufficient. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the core action and the critical safety constraint (nothing sent until confirm_action). The three-paragraph layout is scannable, though the account-permission paragraph could be tightened.

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?

An output schema exists, yet the description still summarizes the return (address, subject, message, listings, action_id), and it covers the prerequisites, limits, and side effects an agent needs. Nothing essential is missing for a 4-parameter mutation tool.

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 coverage is 50%, and the description compensates: it clarifies message is written in the client's language, subject/message are authored by the agent, and property_references are the agency's own or shared MLS listings sourced via match_buyer_to_inventory, capped at 10. The exact reference string format is still left to the schema, so not quite a 5.

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?

States a specific verb and resource (stage an email with listings attached to a client) and immediately scopes what it is not: nothing is sent until confirm_action. An agent can distinguish it from confirm_action, match_buyer_to_inventory, and the other siblings from the description alone.

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 states the workflow condition: stage first, then call confirm_action with the returned action_id after the agent has read it and said yes. It also names match_buyer_to_inventory as the way to source listings, giving a clear alternative path.

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