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. The description adds the OAuth scope 'locations/customValues.readonly' and the explicit endpoint, which is useful authentication context, but it does not describe return format, array shape, pagination, or any other behavioral details. No contradiction with 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 a single concise sentence containing the endpoint and scope with no filler. It is front-loaded and easy to parse, though it mostly restates the title and leaves room for more informative content.

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 simple read-only operation with one parameter and rich annotations, the schema and annotations cover much of the safety profile. However, the description does not explain what custom values are, whether multiple results are returned, or when to choose this over the singular locations_get_custom_value. With no output schema, these gaps are not filled elsewhere.

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 100% coverage for the only parameter, locationId, with the description 'Location Id'. The tool description adds no parameter-specific 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 states the action 'Get' and the resource 'Custom Values', and includes the endpoint [GET /locations/{locationId}/customValues] and the required scope. This makes the operation clear, though it does not explicitly differentiate it from the similarly named sibling tool locations_get_custom_value.

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 such as locations_get_custom_value (singular) or locations_get_custom_fields. Usage context must be inferred entirely from the tool name and endpoint.

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