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

Goes well beyond annotations by disclosing that an empty send_to routes to the account's own phone/email, that the phone is never shown publicly, and that a connected Phorme account owning the place is required. These are concrete behavioral/auth facts annotations do not carry, though return/error behavior is left to the output schema.

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 use case, then the parameter semantics, then the workflow and auth note. Dense but each sentence carries distinct information; slightly long, but no filler.

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 3-parameter mutation tool with an output schema, the description covers trigger, parameter meaning, consent workflow, privacy, and auth prerequisite. Remaining gaps (reversibility, error cases) are minor and partly covered by annotations and the output schema.

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 already 100%, so 3 is the baseline. The description still adds value the schema does not fully capture: "one at a time" (single-recipient constraint) and the meaning of an empty send_to, plus the confirmation sequencing tied to owner consent.

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+resource: setting where booking/ask notices for a place get sent. The example ("text my bookings to my phone") and the title make the intent unmistakable, and it is clearly distinct from sibling set_owner_email by scoping to booking notices rather than the owner's contact email.

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?

Gives a clear trigger ("Use this when an owner wants booking and ask notices for a place sent somewhere else") and a required workflow ("Read it back to the owner first, and set confirmation to true only after they said yes"). It does not name alternative tools, so it stops short of full when-not/alternatives guidance.

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