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

Annotations mark this as non-read-only, destructive and open-world, but the description adds substantial context beyond them: PII prohibitions (no patient names, DOB, medical details), the unverified-claims treatment of name/email, that nothing is emailed from here, the returned token, and its 24-hour expiry with anyone-holding-it-can-read semantics.

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?

It is a dense, front-loaded paragraph where each sentence carries safety-relevant information, but the consent rules are partially restated from the schema, adding mild redundancy. Overall well-organized despite its length.

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?

Although an output schema exists, the description proactively explains the token's purpose, lifetime and follow-up behavior, plus the consent and PII constraints. Nothing an agent needs to invoke this correctly appears missing.

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 100%, so the baseline is 3, but the description adds genuine meaning: it explains that token enables follow-up in the same conversation (omit to start new), and elaborates consent and message restrictions beyond the field-level text.

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?

It states a specific verb+resource (send Tabflows a message on behalf of the person you are helping) and clarifies that Autopilot answers while the team may also respond. It also distinguishes itself from check_reply by explaining the token handoff, so an agent can tell the two apart without opening either schema.

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?

Explicit when-to-use conditions are given: set consent true only after explicit agreement, never infer/invent/reuse consent, and every follow-up needs fresh consent. It also routes the agent to check_reply for reading answers and explains the token-based follow-up path, leaving little to inference.

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