get_location

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

No annotations are provided, so the description carries full burden. It implies read-only behavior but does not mention error handling (e.g., what happens if location_id not found), permissions, or side effects. It discloses that the response includes address, hours, and contact info, which is useful but minimal.

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 concise: two brief sentences, no fluff. The first sentence states purpose, the second provides a usage example. Every word earns its place.

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 tool's simplicity (single integer parameter, read-only fetch) and the presence of an output schema (reducing need to describe return format), the description is nearly complete. It could mention that a single object is returned or cover error cases, but overall it suffices.

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?

With only one parameter (location_id) and 0% schema coverage, the description adds minimal value: it says 'by id' which paraphrases the parameter name. The parameter is self-explanatory, but the description could clarify that it expects the unique identifier of the location.

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 tool fetches a single location by ID and lists the included details (address, hours, contact info). It distinguishes from list_locations, which presumably returns multiple 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?

Provides a concrete usage example ('show our downtown location's details') that helps the agent understand when to invoke. However, it lacks explicit guidance on when not to use this tool versus alternatives like list_locations.

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