Send Message

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

The description includes a warning: '⚠️ This sends a real message from your account.' Annotations indicate readOnlyHint=false, and the warning adds behavioral context beyond the annotations, clarifying the real-world impact.

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?

The description is concise and well-structured, with the purpose front-loaded. The Args section is clear, though it slightly duplicates the schema. The warning is effectively placed.

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?

The description adequately covers input and behavior for a simple send action. It mentions return is 'confirmation with message ID', but without an output schema, more detail about the confirmation structure would be beneficial.

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% (baseline 3). The description adds value by explaining that thread_id can be a Freelancer chat link, and that account 'is the account the message is sent FROM', which goes beyond the schema's description.

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?

The description clearly states 'Send a message in an existing Freelancer.com thread' and provides example use cases like 'Reply to thread 12345 saying...'. It distinguishes from siblings such as freelancer_get_messages and freelancer_list_threads.

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?

The description gives explicit 'Use when:' examples and explains the optional account parameter with reference to freelancer_list_accounts. It doesn't explicitly state when not to use, but the examples and context make it clear.

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