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

No annotations are provided, so the description carries the transparency burden. It discloses normalization of abbreviations, province/postcode cross-checking, misspelling repair, confidence scoring, and an `unparsed` list so nothing is silently dropped. It lacks explicit error-handling details, but is otherwise transparent for a parser tool.

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 compact and front-loaded: the first sentence states the core function, the second adds behavioral guarantees, and the third provides usage context. Every sentence contributes value without unnecessary padding.

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?

For a parsing tool with no output schema and no annotations, the description covers the input nature, output components, normalization behavior, confidence score, unparsed fallback, and target use cases. This gives an agent enough context to select and invoke the 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 100%, so a baseline of 3 applies. The description adds useful context about free-form Turkish addresses and cross-checking the province against the postcode, but it does not materially elaborate on the `defaultProvince` parameter beyond what the schema already states.

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 a specific verb and resource: 'Splits a free-form Turkish address into neighbourhood, street, building, floor, flat, district, province and postcode.' This clearly distinguishes it from sibling validation and invoice tools in the Turkish toolset.

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 gives context for when to use the tool: 'Built for shipping, checkout and CRM systems that receive Turkish addresses typed by humans.' It does not explicitly name alternative tools or state when not to use it, but the use-case framing is clear.

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