page_update

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

No annotation contradiction. Adds important behavioral details beyond idempotentHint: explains PATCH merge semantics for data field, that calls without data use PUT full-field replace, and references page_delete_data for deleting keys. Annotations only hint idempotency; description provides the operational logic.

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?

Four sentences: purpose, condition, alternative tools, data behavior. No fluff, front-loaded, each sentence adds unique value.

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 11 parameters, nested data, and no output schema, the description covers prerequisites, alternatives, and behavioral nuances. Sufficient for an agent to understand when and how to invoke the tool correctly.

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?

Despite 0% schema coverage, description adds meaning: lists the updateable fields and clarifies that at least one must be supplied. Provides critical detail about 'data' behavior (merge vs replace). However, not every parameter is individually explained (e.g., layout_id, image_id are assumed from name).

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?

Clearly states 'Update arbitrary fields on a page' with specific verb and resource. Lists concrete fields (title, slug, etc.) and distinguishes from sibling tools by mentioning dedicated page_set_hidden/page_set_layout for specific use cases.

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 states required condition (at least one of listed fields must be supplied). Recommends using page_set_hidden/page_set_layout when appropriate, and explains different HTTP methods (PATCH vs PUT) based on whether data is provided.

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