send_message

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

No annotations provided. Description says 'Post' (mutation) and mentions permission gate. Lacks details on delivery, side effects, or rate limits. Character constraints added.

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?

Concise with clear sections. Examples are helpful but could be shortened. Well-structured with purpose, usage, args, and requirement.

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?

Output schema exists but not detailed. Lacks error handling, confirmation, or effect on order status. Adequate for a simple send action but could mention response format.

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 has 0% description coverage. Description adds crucial info: order_id is Qualia ID, subject length 1-200 chars, body length 1-10000 chars with markdown support. Compensates well for missing schema descriptions.

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?

Clear verb 'Post a message on a title order' with specific examples. Distinguishes from list_messages which reads messages.

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?

Provides concrete use case examples ('send the buyer an update', 'ask escrow to verify'). Mentions capability gate requirement. No explicit when-not-to-use, but siblings imply reading vs. writing.

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