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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive status, so the safety profile is settled. The description adds genuinely new behavioral context — the $0.01 USDC x402 cost, which affects invocation decisions — though it doesn't state what happens on an unparseable address.

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?

Front-loaded with the core operation, followed by the component list, use cases, and cost. Every clause earns its place with no redundancy.

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?

With no output schema, the enumerated component list effectively serves as the return-value description, and the cost note is included. Only failure/edge-case behavior (e.g., partially parseable addresses) is unaddressed for a simple one-parameter 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?

Single required parameter with 100% schema description coverage and a worked example, so the schema carries the semantics. The description's enumeration of components implies the parsing scope but adds no parameter syntax details, which is acceptable at this coverage level.

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 full address string into its components') and enumerates the component set returned. An agent can distinguish this from the many address-matching siblings (address_match, global_address_match) without opening schemas.

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?

It gives clear use contexts ('address cleansing, standardization, geocoding preparation, and loading structured address data'), which tells an agent when this tool fits. It does not, however, explicitly distinguish itself from match/standardize siblings or state when not to use it.

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