locations_create_tag

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds no further behavioral context—it does not disclose what creating a tag entails, whether it can overwrite existing tags, or any permission requirements. It simply repeats the intent without elaboration.

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 words), which is efficient, but it is under-specified and fails to include necessary context. It is not front-loaded with useful information because there is no information beyond the verb and object. It is short but not appropriately sized for an effective tool description.

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 that creates a tag, the description is completely inadequate. It does not explain that it creates a tag for a location, that the name is required, or that locationId defaults to the location context. With no output schema and only minimal parameter docs, the agent is left without any situational understanding of what the tool accomplishes.

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%, so the parameters are fully documented in the input schema. The description adds no additional meaning to either 'name' or 'locationId', so the baseline score of 3 for high schema coverage 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 'Create Tag' directly restates the tool's name (locations_create_tag), which is a tautology. It does state the verb and object, but adds no elaboration on the scope (e.g., that it creates a location tag) or how it differs from sibling tag operations like locations_update_tag or locations_delete_tag.

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?

No information is provided about when to use this tool versus alternatives. There is no mention of prerequisites, contexts, or exclusions. The description gives the agent zero guidance on selecting this tool over other create or tag-related operations.

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