get_value

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses that output is serialized and automatically truncated above 10KB, but it does not state what happens for invalid paths, missing aliases, or unloaded documents.

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 front-loaded with the purpose and appropriately sized for a two-parameter tool. The Args and Returns sections are useful, though the return value repeats the truncation note already stated above.

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?

This is a simple read operation and an output schema exists, so return-shape details are not required. The description covers alias, path syntax, root behavior, and truncation, but it omits error behavior for invalid paths or unloaded aliases.

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 0%, so the description must carry parameter meaning. It does so for both parameters: alias identifies the loaded document, and path uses dot/bracket notation with an empty string meaning root.

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 specific verb and resource: retrieve the value at an exact path in a loaded JSON document. It is clear on its own, but it does not explicitly distinguish itself from close siblings such as jsonpath_query, get_type, or get_keys.

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 phrase 'exact path' implies usage when the caller knows the precise location, and the 'loaded document' wording implies load_json must precede it. However, there is no explicit when-to-use or when-not-to-use guidance compared with jsonpath_query or other sibling tools.

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