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

With no annotations provided, the description carries the full burden and excels by explicitly stating pure local computation, no upstream calls, microsecond latency, and deterministic output. It also mentions that it resolves richer info beyond a simple boolean, setting clear behavioral expectations.

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 tight and well-structured: the first paragraph explains what the tool validates, and the second adds value-added resolution and performance characteristics. No redundant or irrelevant content.

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 a simple input schema and no output schema, the description covers the tool's scope, the extra resolution it performs, and its non-network, deterministic behavior. It provides sufficient context for an agent to know what to expect from calling it.

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 coverage is 100%, so baseline is 3. The type parameter description ('Omitted → inferred from the format') and the tool's list of supported formats add meaningful context about how the value is interpreted. The value description is minimal but the overall purpose makes it clear enough.

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 that the tool validates a specific list of Turkish identifiers and numbers, with type auto-detection, from a single endpoint. The title reinforces the purpose, and the enumeration of supported types distinguishes it from more specific sibling validators.

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 usage when the type is unknown or multiple types are involved, but it does not explicitly compare with dedicated validators like iban_validate or isbn_validate. There is no direct 'when not to use' guidance, leaving the decision to inference.

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