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

Annotations already declare non-readOnly, non-idempotent, openWorld. The description adds real value beyond them: an authentication requirement with its source tool, and a 10-1000 character constraint on the payload. It still omits failure behavior and whether a match must be in a particular state.

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?

Two short sentences, no filler. The auth prerequisite leads and the action follows, which is compact, though placing the requirement before the purpose slightly delays the core action.

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?

No output schema exists, and for a simple send tool the description covers authentication and payload bounds. It is missing only edge-case behavior (invalid match, blocked agent, rate limits), which keeps it short of full completeness.

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. The description does add the body length constraint (10-1000 chars) that the schema's "Intro text" description lacks, but adds nothing about match_id semantics beyond what the schema states.

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 ("Send a short intro") plus the target (a matched agent) and a concrete length bound. It partially differentiates from the closest sibling send_match_message by framing the payload as an intro, though it never explicitly contrasts the two.

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 one useful prerequisite — api_key from register_agent — and implies the recipient must already be a match. It does not say when to use this versus send_match_message or what match state is required, so the agent must infer the routing.

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