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

With no annotations, the description carries the full burden. It usefully discloses coverage ('all 404 NANP codes in use, including overlays') and pricing ('x402 price $0.01/call (USDC, eip155:8453)'), which is real behavioral context. However, it says nothing about auth requirements, rate limits, error behavior, or what the dual-mode response looks like.

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 first two sentences are tight and front-loaded. The third sentence is syntactically broken ('needs to all 404 NANP area codes → state lookup') and repeats coverage already stated, and the trailing price string is grafted on awkwardly.

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 three-parameter lookup with no annotations and no output schema, the description covers coverage scope, the two modes, and cost. It stops short of describing return shape (state name? list of codes?) or how to disambiguate when both code and state are supplied, leaving gaps an agent would hit at call time.

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 baseline is 3. The description's dual-mode framing ('look up ... or list every area code in a given state') corroborates the code/state parameters, but it adds no syntax or format detail beyond the schema and does not address why all three parameters are marked required when the modes appear mutually exclusive.

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?

States a specific verb and resource: 'look up any US telephone area code to find the state or territory it serves, or list every area code in a given state.' That is clear and distinguishable from calculator/converter siblings. It doesn't explicitly name a sibling to differentiate against, but the purpose is unambiguous.

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 only guidance is the garbled fragment 'Use this when an agent needs to all 404 NANP area codes → state lookup,' which restates the purpose rather than telling the agent when to pick this tool over alternatives. No when-not conditions, no prerequisites, no alternative tools referenced.

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