Dump Raw BaseContainer

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

No annotations are provided, so the description carries the full burden. It discloses that the tool dumps raw container data including hidden keys, and suggests filtering. It does not mention read-only nature or potential size of output, but the behavior is mostly transparent for a dump 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?

The description is two short sentences that are front-loaded with the core purpose and a practical usage tip. Every sentence serves a clear function, with no unnecessary words.

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 3 well-described parameters and no output schema, the description covers the purpose but omits information about the return format or potential data volume. For a dump tool, it is adequate but could hint at the output structure.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the purpose of the id_from/id_to parameters ('Filter by key range to narrow output'), which goes beyond the schema's type constraints.

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 clearly states the tool dumps the raw BaseContainer of a C4D entity, including hidden keys not shown in describe, and mentions filtering by key range. This verb and resource are specific and distinguish it from siblings like describe or get_params.

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 implies when to use (to see hidden keys) and provides a tip on filtering. However, it does not explicitly state when not to use or name alternatives, though the context of sibling tools makes the purpose clear.

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