Get Locations (Exact Match)

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds that it returns exact matches and supports multiple lookups, which is consistent but not significantly expanding on annotations.

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?

Description is extremely concise: two sentences for purpose and batching, plus a minimal Args list. No wasted words, front-loaded with key 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?

Given the simple lookup nature, full schema coverage, and comprehensive annotations, the description is adequate. It covers exact matching, batch capability, and parameter structure. No output schema, but the return type is implied.

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% and the description's parameter documentation ('Array of suburb/postcode pairs to look up exactly') mirrors the schema. It adds no new meaning beyond what the schema already provides.

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 tool name and title clearly indicate exact match location lookup. Description specifies 'exactly match provided suburb/postcode combinations', distinguishing it from fuzzy search siblings like machship_search_locations.

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?

Description states supports multiple lookups per call, implying batch usage. It does not explicitly contrast with alternatives like machship_search_locations or machship_get_locations_with_options, but the name and description make the exact-match use case obvious.

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