Get Parameter Values

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

No annotations are provided, so the description carries full burden. It clearly states it is a read operation ('read parameter values'), explains the id syntax with examples, and describes the return format. It does not mention side effects or permissions, but the read-only nature is clear.

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 core purpose, then efficiently explains the complex id parameter with examples. Every sentence adds essential information without redundancy. It is appropriately sized for the tool's complexity.

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 no output schema, the description specifies the return format {values: [{path, value}]}. It covers handle shapes in detail and explains id discovery via `describe`. The description is complete for a read tool with complex input requirements.

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 has 100% description coverage, but the tool description adds substantial value beyond the schema's concise parameter descriptions. It explains the flexible id formats (int, list, with sub-component access and explicit dtypes) and provides concrete examples, making parameter usage much clearer.

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 explicitly states it reads parameter values on C4D entities by id or DescID path, with detailed examples of id formats and mention of the return structure. It distinguishes from sibling tools like `describe` and `set_params` by referencing `describe` for id discovery.

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 advises to discover ids via `describe`, implying a typical workflow. However, it does not explicitly state when to use this tool over alternatives like `get_container` or `sample_transform`, nor does it provide clear 'when not to use' guidance. The hint is helpful but not exhaustive.

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