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

Beyond the annotations, the description discloses credit cost, when charging occurs, expected duration, that the new kit requires user review, and retry behavior. These are material behavioral details for a costly mutation tool and are consistent with destructiveHint=true.

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 purpose and behavior, then moves through cost, duration, sibling guidance, retry prohibition, and return values. Every sentence conveys actionable information with no wasted text.

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?

Given the tool's cost, delay, mutation behavior, and sibling alternatives, the description provides all context an agent needs before invoking it. It also names the returned fields even though there is no output schema.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains website_url adequately. The description reinforces that it reads a public website but adds no further syntax or format detail beyond the 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 states a specific verb and resource: reading a public website and saving its brand assets as a new brand kit. It clearly distinguishes this extraction flow from retrieving existing kits by directing the agent to check list_brand_kits first.

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 explicit routing guidance: call list_brand_kits first and reuse a matching website's kit unless the user explicitly wants another extraction. It also states a clear retry prohibition: do not call this again to retry.

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