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

Goes well past the destructiveHint/openWorldHint annotations by naming exactly what is destroyed ("overwrites example slots 1 onward", "clears leftover starter text"), what side effect occurs (the handle is saved to the profile), the rate limit (10/day), and the price (100 credits). That is the full behavioral profile an agent needs before a costly, destructive call.

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?

Front-loaded with the operation, then side effects, then the alternative and cost. Every clause carries information, but the paragraph is dense and chains many clauses into a single flow, which makes scanning slightly harder than a short bulleted ordering would.

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?

No output schema exists, yet the description enumerates the return payload (slots overwritten and cleared, failed posts, cost, credits left). Combined with cost, rate limit and side effects, nothing material is missing for a destructive, credit-consuming operation.

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 baseline is 3; the description adds rationale the schema lacks, notably the warning that passing a handle saves it to the profile and therefore must be the creator's own, plus the credit implication of the 5-post cap. The ordering semantics of posts are already in the schema, so this is reinforcement rather than new meaning.

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?

"Turns up to 5 of the creator's own posts into voice examples" states a specific verb, resource and scope, and immediately disambiguates from update_voice_examples and list_my_posts by naming both. An agent can route this without opening the schema.

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?

Explicit prerequisite ("Use list_my_posts first to get the urls and texts") and an explicit alternative with a selection condition ("for pasted text use update_voice_examples (free)"). It also constrains inputs ("pass only the creator's own handle"), covering when-not as well as when.

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