create_location

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

No annotations are provided, so the description must carry the behavioral burden. It adds useful context that IT Glue typically requires a country_id even though it is optional in the schema. However, it does not disclose side effects, return value, or failure modes for a write operation, so transparency is partial.

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 filler. The first sentence states the action and scope, the second highlights a key requirement. Every word earns its place, and it is front-loaded with the core purpose.

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 tool with 12 parameters, no output schema, and no annotations, the description is functional but lean. It covers the core purpose and one gotcha, but lacks information about return values, error conditions, or how to choose this over sibling create/update tools. It is minimally adequate.

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 input schema already has 100% description coverage for all 12 parameters. The description only reiterates that name and country_id are important, which is already captured in the schema's required list and the country_id property description. No additional parameter semantics are provided beyond the schema.

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's function with a specific verb+resource: 'Create a new location (physical address/site) for an organization in IT Glue.' This distinguishes it from sibling tools like update_location, search_locations, and get_location, and it also clarifies the scope (for an organization).

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 when to use this tool (when creating a new location) by using the verb 'Create' and adding requirements ('requires a name and typically a country_id'). It does not explicitly mention alternatives or when not to use it, but the purpose is unambiguous enough that an agent would not confuse it with update or search operations.

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