clean_person

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

No annotations are provided, so the description carries full burden. It only states the basic function and cost implication, but does not disclose what happens on validation failure, whether it returns results per field, or any side effects. The return behavior is completely opaque.

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 short sentences, no wasted words. First sentence states purpose, second adds key cost benefit. Well structured for quick understanding.

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?

Although the schema covers parameters, the description lacks information on return values, error handling, and the fact that no parameters are required contradicts the 'full record' implication. Without an output schema, more behavioral context is needed for a tool with 6 parameters.

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 input schema already has 100% coverage with descriptions for all 6 parameters. The description adds no additional semantic value beyond grouping them as 'FIO + birthdate + address + phone + email + passport', which is evident from the parameter names. Baseline of 3 is appropriate.

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 verb 'validate' and the resource 'full person record'. It distinguishes from sibling tools by highlighting the batch nature and cost savings compared to separate calls to individual cleaners like clean_address, clean_name, etc.

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 explicitly states when to use this tool: for validating a full person record in one request, and mentions cost benefits. However, it does not explicitly state when not to use or mention alternatives, though the sibling list implies them.

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