Vehicle Number Check

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by specifying that letters and separators are ignored, that reduction uses numeric digits only, and that the response follows the same harmony schema as mobile analysis. It stops short of summarizing actual error modes beyond linking to the external error contract.

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 well structured into WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH, and a documentation link. Each sentence serves a clear purpose, and the most important behavioral details are front-loaded in the opening sentence.

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 description provides invocation context, expected input normalization, sibling-tool disambiguation, a recommended predecessor, and a pointer to the full output and error contract. Since the input schema is fully documented and an output schema exists, the description does not need to restate return values and is complete for an agent selecting and calling this tool.

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 100%, so the schema already documents all four parameters. The description adds value by explaining the input contract for the vehicle_number parameter — letters and separators are stripped and only digits participate in reduction — which is not fully explicit in the individual property descriptions. This complements rather than merely repeats the schema.

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 uses a specific verb and resource: it strips non-digits from a vehicle registration token, reduces the numeric run with owner name and birth date, and returns a harmony schema. It clearly differentiates itself from asteroids mobile-number checking and business-name analysis, so an agent can identify this tool without opening the schema.

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 WORKFLOW section explicitly recommends running asteroid_get_numerology_profile before this tool and states AFTER: None. The DO NOT CONFUSE WITH section names two siblings and explains why they are not appropriate, which gives an agent concrete guidance on when to choose this tool over alternatives.

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