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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds genuinely new behavioral context: the block becomes public immediately on save, the user must be asked to confirm, and payments settle to the business's own Stripe account outside this chat. It does not cover failure modes or auth requirements.

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?

Dense but front-loaded: the action is stated first, then the type/data reference block. Every line is load-bearing given the nested payload, though the opening store-administration framing sentence is slightly wordy.

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 mutation tool with annotations but no output schema, the description covers what is being created, the full payload vocabulary, and the public-visibility consequence. It stops short of stating permission prerequisites or the returned block identity, which an agent might want.

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%, but the schema explicitly defers to the description ('the data each type takes is described above'), so the per-type payload shapes (link, text, video, booking, socials, product, including style enums and network lists) are the real semantic content and exist only here. Only workspaceId/idempotencyKey details are left to 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?

Specific verb+resource: 'Append a block at the bottom of the public store page' names the exact mutation and its placement. It is clearly distinguishable from siblings like update_store_block (modify existing), reorder_store_blocks (reorder), and delete_store_block.

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 frames the context (owner-managed link-in-bio store, no commerce in chat) and gives one operational rule ('It is public as soon as it is saved: confirm with the user'), but never explicitly routes the agent to alternatives such as update_store_block or reorder_store_blocks. Usage is implied rather than stated.

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