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

Beyond annotations, it discloses the exact fee, the two payment rails and prohibition on using both, preflight balance display, whole-list trait replacement by revise_kind, non-random variant selection, and a one-wake-key restriction. These are substantive operational and cost behaviors that an agent would not infer from the annotations alone.

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 key information is front-loaded: purpose/fee first, then parameter constraints, then payment workflow and edge cases. It is dense and could be easier to scan with structure, and 'Lost? Call front_door' is optional, but nearly every sentence carries a real constraint for this complex 9-parameter tool.

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 complex paid mutation with no output schema, it covers the critical call path: cost, preflight, payment rail choice, parameter constraints, law-trait refusals, and fallback to front_door. It still does not state what a successful call returns or any permission/ownership prerequisite beyond owner-written descriptions, so it is strong but not fully complete.

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?

With only 44% schema description coverage, the description supplies semantics for most parameters: name normalization/uniqueness, description limits, traits as a whole existing-trait list, recipe uniqueness/quantity/total/byte limits, drawing shape delegation to draw_self, variant ownership/state/name uniqueness, and city_credit_request_id payment use. It leaves only low-level drawing palette/indices shape to the schema and draw_self, so it substantially compensates for the coverage gap.

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 opening sentence gives a specific verb and resource ('Invent a public kind') and states the exact $1 fee. It implies the create-vs-revise split by noting a later revise_kind replaces traits whole, but it does not explicitly contrast with other creation-adjacent siblings such as make or found.

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 concrete usage context: call credit_preflight before a credit-funded invention, use exactly one payment rail, and take the suggested_request_id from credit_preflight. It also names revise_kind for later whole-replacement and front_door as fallback, plus law-trait exclusions, though it does not spell out the full when-not matrix among all creation siblings.

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