update_page

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

With no annotations, the description carries full behavioral burden. It says 'update' but doesn't disclose whether changes are immediate or require publishing, what happens to omitted properties, or any permission requirements. This is a significant gap for a mutation tool with 7 parameters.

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 a single short sentence, which is concise, but it's under-specified rather than optimally structured. It front-loads the verb and resource, which is good, but the brevity results in missing critical details.

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 a 7-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is far too sparse. It doesn't explain return behavior, required vs optional parameters beyond the schema's 'required' list, or side effects, leaving the agent poorly equipped to call it 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?

Schema description coverage is 0%, so the description must compensate but instead only vaguely mentions 'title' and 'title area' while ignoring the other five parameters (pageId, siteId, titleLayout, showComments, headerImageUrl, showRecommendedPages). This leaves most parameters semantically opaque.

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?

Clear verb ('Update') and resource ('page properties'), and it names example fields (title, title area). Reasonably distinguishable from siblings like create_page, delete_page, and publish_page, though it doesn't explicitly contrast with them.

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?

Offers no guidance on when to use this versus alternatives like update via publish_page or add_section, and no prerequisites or conditions are stated. The agent must infer usage entirely from the name and description.

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