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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real behavioral context beyond them — the $200 state fee, county-dependent publication cost, optional add-ons, and the $10-per-LLC discount after the first when ordering up to 10. It stops short of describing how the quoted total is returned.

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?

One dense pricing sentence followed by a short usage sentence; the highest-value facts (what is priced, add-ons, discount) are front-loaded. The first sentence is long but each clause carries pricing information an agent would otherwise miss.

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 read-only quoting tool with rich annotations and full parameter documentation, the description supplies the pricing model an agent needs to answer cost questions. With no output schema, it would be slightly stronger if it noted that the response is a per-line breakdown with a total.

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 the schema already documents each field; the description still adds cross-parameter meaning by tying own_county to higher publication cost and count to the multi-LLC discount, and framing dba/ein/profession as optional add-ons rather than standalone flags.

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: pricing LLC/PLLC formation plus mandatory publication in New York, broken out line by line. It is clearly distinguishable from siblings like get_publication_price (publication only) and start_order (placing the order).

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?

"Use when someone plans to form an LLC and asks what it costs" gives an explicit trigger condition. It does not, however, name which sibling to use instead when the user only wants publication pricing or wants to actually place the order.

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