layout_asset_update

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

Adds key behavioral info beyond annotations: filename is read-only and causes 500 error. IdempotentHint already indicates safety, but description provides concrete constraint.

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?

Two sentences, no wasted words. Action first, then critical constraint. Efficient and front-loaded.

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 4 parameters and no output schema, description covers primary purpose and critical constraint. Lacks info on response or prerequisites, but sufficient for basic usage.

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 25% (only filename has description). Description adds that filename is read-only and suggests alternative, but does not explain 'site', 'asset_id', or 'data' parameters. Partially compensates for low coverage.

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?

Description clearly states it updates a layout_asset's content via PUT. Specifies verb and resource, and distinguishes from sibling tool 'asset_replace' for renaming.

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?

Explicitly tells when to use (update content) and when not to (rename, use asset_replace). Warns against sending filename. Could mention other usage contexts, but adequate.

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