locations_create_custom_value

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

The description does not contradict the annotations (readOnlyHint=false, so a mutation is expected), but it adds no behavioral details beyond the annotations. It does not mention any side effects, permissions, or reversibility, so it contributes nothing beyond what structured fields already communicate.

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 terse (three words), which is under-specification rather than effective conciseness. It lacks any explanatory structure, so the brevity is not a virtue here.

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 there is no output schema, three parameters, and a minimal description, the tool definition is severely incomplete. An agent would not know what this tool does, what the parameters mean, or what to expect, making it nearly unusable without external knowledge.

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 has 33% description coverage (only locationId has a description), and the tool description provides no parameter information. The meaning of 'name' and 'value' is entirely undocumented, and the description does not compensate for this gap at all.

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 Custom Value' essentially restates the tool name without providing any additional specificity about what a custom value is or how it relates to locations. It does not distinguish this tool from siblings like locations_create_custom_field or locations_create_tag, making the purpose vague.

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?

There is no guidance on when to use this tool versus alternatives. The description gives no context about the use case, prerequisites, or scenarios where this tool is appropriate, leaving the agent without clear direction.

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