send_address_message

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

With no annotations, the description carries the full burden of behavioral disclosure. It is a single phrase with no mention of side effects, permissions, response format, or whether this mutates state. The tool clearly sends a message, but no behavioral details are disclosed.

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 extremely short, but this is under-specification rather than effective conciseness. It merely restates the tool name with a synonym and provides no useful structure or additional information.

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 tool with 4 parameters, no annotations, and no output schema, the description is entirely inadequate. It fails to explain the message format, required vs optional params, how phone/chatId are used, or the expected behavior. The single phrase provides almost no context for an AI agent to correctly select and invoke the tool.

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 description coverage is 0% and the description does not mention any parameter. The schema lists body, phone, chatId, and quotedMsgId without descriptions, and the description neither explains the role of body nor how the other parameters relate to an address request. The description adds no parameter meaning.

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 'Send address request message' adds 'request' to clarify the tool sends a request for an address, not just an address. It distinguishes somewhat from siblings like send_location_request or send_message, but the purpose remains vague because it does not explain what an address request message is or what triggers it.

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?

No usage guidance is provided. The description gives no indication of when to use this tool versus similar send_* siblings such as send_location_request, send_contact, or send_message. There is no context about prerequisites or alternative tools.

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