Get Parameter Values

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

With no annotations, the description carries the full behavioral burden. It explicitly states the operation is a read, specifies the exact return shape `{values: [{path, value}]}`, preserves request order, and explains dtype inference and override syntax. This is highly transparent for a read-only tool.

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?

Four dense sentences, each earning its place: purpose, id grammar, explicit dtype syntax, return contract and discovery hint. No filler or repetition of schema details.

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?

The description provides the return contract even though no output schema exists, explains the parameter path grammar thoroughly, and points to `describe` for id discovery. Combined with the detailed handle schema, an agent has enough to select and invoke the tool correctly.

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?

Although schema coverage is 100%, the description adds critical semantics beyond the schema: valid id forms, chained DescIDs, 'x'/'y'/'z' vector sub-components, and explicit dtype tuples. This is essential for constructing correct `ids` payloads and is not inferable from the raw schema alone.

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 opens with a specific verb and resource: 'Read parameter values on a C4D entity'. It clearly distinguishes this as a read operation from siblings like set_params, and 'Discover ids via describe' positions it relative to the discovery tool.

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 read context is clear, and it explicitly directs the agent to `describe` when ids need to be discovered. However, it does not explicitly state when to avoid this tool or prefer alternatives like set_params, so it lacks explicit when-not guidance.

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