distill_schema

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

The description discloses the two different modes and their effects, which provides adequate transparency. However, it does not mention what the output format looks like or any error conditions, leaving some gaps given the absence of annotations.

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 extremely concise, consisting of two efficient sentences that front-load the purpose and then detail the modes. No wasted 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 the tool's simplicity (3 parameters, no output schema), the description is moderately complete. It covers the primary functionality but omits details on output and error handling that would be helpful for an AI agent.

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 description explains the 'mode' parameter in terms of its effects (compact vs minimal) but does not clarify the 'keep_required' parameter or the expected format for the 'schema' input string. With 0% parameter description coverage, more detail is needed.

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's purpose: reducing token overhead of schemas. It specifies two modes (compact and minimal) and what each does, making the action unambiguous.

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 the tool (to reduce schema size) but does not provide explicit guidance on when not to use it or how it compares to sibling tools like distill_json or distill_conversation.

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