get_location

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

With no annotations provided, the description carries the full burden. It clearly indicates a read operation via 'Get' and mentions return content, but it does not disclose additional behavioral traits such as authorization requirements, error handling, or side effects. For a simple retrieval, this is minimally acceptable.

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 sentence that front-loads the action ('Get'), resource ('location'), and scope ('by ID') without any filler. It is concise and well-structured.

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 simple with only one parameter and no output schema. The description states what it retrieves and highlights key returned fields (address, phone number), which is sufficient for a basic get operation. It lacks mention of edge cases like not found, but that's not essential here.

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 100% coverage for the single parameter 'id' with a clear description. The tool description adds no extra meaning beyond 'by ID', which is already implied. The description does not compensate for missing schema info because there is no missing info.

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 uses a specific verb 'Get', identifies the resource 'location' from IT Glue, and specifies the scope 'by ID' along with key return fields ('full address and phone number'). This clearly distinguishes it from sibling tools like search_locations, which is for searching.

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 that this tool is for retrieving a single location when you have its ID, but it does not explicitly mention when to use it versus search_locations or other alternatives. There is no explicit when-not-to-use guidance.

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