summarize_object

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

Adds returns format (dot notation), circular reference detection, and depth/property limits. Annotations already confirm read-only/idempotent; description enriches beyond.

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?

Purpose sentence first, then critical state requirement, then output format, then parameter list. No redundancy, efficient.

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?

All necessary context: state requirement, parameter sources, limits, and output format. No output schema needed given description clarity.

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 has 0% description coverage; description compensates fully with clear meaning for each parameter, including defaults and max values.

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?

Clear verb 'Produce a flattened summary' specifies exact output. Distinguished from siblings like evaluate_expression by focusing on flattening complex objects.

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?

Specifies prerequisite: State STOPPED and source for variables_reference. Could mention alternatives for simple evaluations but otherwise strong.

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