Get custom value

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no additional behavioral context such as return format, error cases, or what constitutes a 'custom value'. It simply restates the operation without adding insight beyond 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, front-loaded sentence with no wasted words. It is appropriately terse for a simple get operation, though this economy comes at the cost of missing essential details captured in other dimensions.

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 absence of an output schema and the sparse description, an agent is left without knowledge of the return structure or how this tool differs from closely related ones like ghl_get_custom_field. The description does not cover error handling, presence of results, or any operational nuances, making it incomplete for reliable invocation.

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 covers only 50% of parameters (locationId has a description, customValueId does not). The description's 'by id' redundantly refers to customValueId but does not clarify its format or meaning. It fails to compensate for the missing schema documentation, leaving the agent to infer the id's nature.

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 'Fetch a single custom value by id.' is specific with a clear verb (fetch), resource (custom value), and method (by id). The word 'single' distinguishes it from list operations, though it does not explicitly name a sibling alternative.

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 guidance is given on when to use this tool versus alternatives like ghl_list_custom_values or ghl_get_custom_field. The description implies a get-by-id scenario but does not state exclusions or provide routing to siblings.

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