locations_get_custom_values

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the description is relieved of repeating those. However, the description adds no extra behavioral context: it doesn't explain what data is returned, any side effects, or anything beyond what the annotations convey. With annotations present, the bar is lower, but the description still fails to add value.

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 simply 'Get Custom Values'—brief and without fluff, which is concise. However, it is under-specified to the point that it does not earn its place; it fails to convey the tool's purpose clearly. Conciseness should be paired with informativeness, which is lacking 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 the tool has only one optional parameter and no output schema, a complete description should at least clarify what 'custom values' are and how they relate to the location. The current description leaves this ambiguous, especially with the singular sibling tool. The annotations cover safety, but the description is incomplete for effective use.

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 fully documents the single parameter 'locationId' with its default behavior, achieving 100% schema description coverage. The description itself adds no additional meaning about the parameter. Since the schema carries the weight, a baseline 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 states a verb ('Get') and a resource ('Custom Values'), making the basic intent clear. However, it is vague about what 'Custom Values' refers to in this context, and there is a sibling tool 'locations_get_custom_value' (singular) that could easily be confused with this one. The description does not differentiate between the two, so the purpose is only partially clear.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any context, exclusions, or alternative tools. An agent has no basis for choosing this over the singular 'locations_get_custom_value' or other related tools.

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