Describe C4D Entity

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

With no annotations, the description covers basic behavior: it dumps parameters and lists what is returned. However, it does not address side effects, error conditions, or return format details. The behavioral disclosure is adequate but not comprehensive.

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?

Two concise sentences—one for purpose, one for usage guidance. No redundant words or filler. Efficiently communicates the essential information.

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 complex handle parameter and lack of output schema, the description does not fully describe the return structure beyond listing fields. For a data-dumping tool, more detail on the output format would improve completeness. Still, it covers the core need for parameter discovery.

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 100%, so baseline is 3. The description adds that the entity is 'resolved by handle' but does not elaborate on the handle syntax beyond what the schema already details. The schema itself provides extensive parameter semantics.

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?

Description clearly states 'Dump all description parameters of a C4D entity' with a specific verb and resource. It contrasts with sibling tools like get_params and set_params by emphasizing discovery of parameter IDs before reading/writing.

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 'Use this to discover parameter IDs before reading/writing' provides clear context for when to use the tool. It does not explicitly mention when not to use or list alternatives, but the purpose implies its role among siblings.

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