Get IT Glue Location

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

Annotations already provide key behavioral hints (read-only, open-world, idempotent, non-destructive), so the description adds minimal value beyond stating it returns 'Location details including full address'. It does not disclose additional traits like rate limits, authentication needs, or error handling, but does not contradict 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?

The description is front-loaded with the core purpose, followed by a structured Args and Returns section. Every sentence is necessary and contributes to understanding, with no wasted words or redundancy.

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 tool (2 parameters, 100% schema coverage, rich annotations) and no output schema, the description is reasonably complete. It specifies the return content ('Location details including full address') and parameter usage, though it could mention format details for the output (e.g., structure of details).

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%, with clear descriptions for both parameters (e.g., 'id' as 'The unique ID of the resource', 'response_format' with enum and default). The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 ('Get a single location by ID') and resource ('Location'), distinguishing it from sibling tools like 'itglue_list_locations' (which retrieves multiple locations) and 'itglue_create_location' (which creates rather than retrieves). The verb 'Get' is precise 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 implies usage context by specifying 'by ID', suggesting it should be used when you have a specific location identifier. It does not explicitly state when not to use it or name alternatives, but the context is clear enough to differentiate from list operations.

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