Send Location

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

The description merely restates the core action without adding behavioral context beyond what annotations already declare. It does not disclose any behaviors such as how the location pin is rendered, whether confirmation occurs, or any rate limits or dependencies, despite annotations indicating a write operation (readOnlyHint=false).

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 a single, concise sentence that front-loads the main action and recipient. Every word contributes, with no redundant or filler content.

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 tool is relatively simple, and the schema covers all parameters. However, the description does not explain how a location pin is generated from latitude/longitude or how the optional name/address are used. With no output schema, a bit more context about expected behavior (e.g., whether coordinates are required and how the pin appears) would improve completeness, but the current level is minimally adequate.

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 100%, so the schema fully documents every parameter. The description adds no additional meaning beyond what the schema provides, which aligns with the baseline score of 3 for high coverage.

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 the specific action ('Send a WhatsApp location pin') and the target ('to a phone number'), distinguishing it from sibling tools that send other media types like text, audio, or media. The verb and resource are specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives like send_media or send_text. It does not mention any conditions, prerequisites, or exclusions, leaving the agent without context for choosing this tool over siblings.

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