maps_select_result

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

With no annotations, the description carries the transparency burden. It discloses that the tool operates on a stateful UI (currently displayed results), uses a zero-based index, and is not a generic click. It doesn't explain the downstream effects of selecting, but the key behaviors are communicated effectively.

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 two sentences with no redundancy. The first sentence states the core function and key details, while the second provides an important limitation. Every word contributes to understanding.

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 simple tool with one parameter and no output schema, the description adequately covers the action, state requirement, and a key limitation. The only gap is the lack of detail about what happens after selection, but this is likely non-essential for invoking 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?

The schema has no description for 'index', so the description's addition of 'zero-based' is critical semantic information. This clarifies that the integer refers to the position in the displayed list, complementing the schema's min/max constraints.

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 specifies the action ('Select'), the object ('currently displayed Google Maps place results'), and the indexing scheme ('zero-based index'). It also distinguishes the tool from a generic browser click, which helps differentiate it from potential misuse and sibling tools like maps_select_route.

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 implies the tool should be used when place results are displayed and explicitly excludes generic clicking behavior. However, it does not name alternative tools or provide direct 'when to use' instructions beyond the context of 'currently displayed' results.

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