refine_schema

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions 'conversation' but does not explain iterative behavior, side effects, authentication requirements, or any constraints. The single sentence is insufficient for a tool with two complex parameters.

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 (5 words) but at the cost of essential detail. Given the tool's complexity (two required nested objects), the description should be longer and front-load critical information. The brevity is more under-specification than efficient conciseness.

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 tool has an output schema but the description ignores it. With 0% schema parameter coverage, no usage guidelines, and minimal behavioral context, the description is grossly incomplete for an agent to use this 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?

Schema description coverage is 0%, and the description provides no explanation for the 'messages' or 'current_schema' parameters. The agent receives no guidance on format, purpose, or constraints beyond the schema's structural definitions.

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 states 'Refine an existing schema via conversation,' which identifies a specific verb and resource. However, it does not differentiate from the sibling tool 'propose_schema' and lacks detail on what 'refine' entails (e.g., field additions, type changes).

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?

No guidance is given on when to use this tool versus alternatives like 'propose_schema' or 'generate_data.' The phrase 'via conversation' implies interactivity but provides no explicit context or exclusions.

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