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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known. The description adds substantial behavioral context: creating a free public trait, the ability to make it inert by omitting recipe, and detailed limit constraints (128 effects, 8 nested levels, byte size, timer ranges). This goes beyond annotations without contradicting them.

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 front-loaded with the main verb, but it becomes dense and includes tangential navigation pointers ('Full catalog: /api/tools', 'Lost? Read the city front door...') that are not essential for invoking this tool. While organized, it could be tightened by moving the help pointers out of the core definition.

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?

The input constraints are exceptionally thorough (name, description, recipe, physics limits), but the description does not mention what happens on success, what the tool returns, or error conditions like name collisions. With no output schema, this gap leaves the agent uncertain about post-call behavior.

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 only 33% (only recipe has a schema description). The description compensates strongly: it explains name uniqueness and normalized format, description default and max length plus 'safe characters', and recipe forms (array shorthand or object keyed by specific verbs) with constraints. All three parameters receive meaning beyond the raw schema.

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 opens with 'Coin a free public trait,' which is a specific verb (coin) and resource (trait), and adds 'free public' to distinguish it from private or paid creation tools. This clearly differentiates it from siblings like invent_kind or make, which target different entities.

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 offers guidance on prerequisites ('Read physics first') and points to help tools (front_door), but it does not explicitly state when to use this tool versus alternatives like invent_kind or make. There are no exclusions or contrast with sibling tools, so usage remains implied rather than explicit.

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