update_page

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

With no annotations, the description carries the full burden. It discloses a meaningful trait (publish state untouched) beyond the schema. However, it omits other behavioral details such as return values, permissions, or side effects expected from a mutation tool.

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, front-loaded sentence with no redundant words. Every element ('update', 'title and/or body', 'publish state left alone') carries meaning.

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?

The description is adequate for basic use, identifying the updatable fields and a key behavioral constraint. However, for a write tool with no output schema and no annotations, it lacks information about return values, permissions, or error conditions, making it incomplete for an agent to fully understand the outcome.

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. It adds context for 'title' and 'body' (updatable fields), but the required 'course' and 'slug' parameters are not explained at all. This is only partial compensation for the missing schema descriptions.

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?

The description clearly states a specific action ('Update a page's title and/or body') with a distinct resource and verb. It differentiates from sibling tools like create_page and get_page, and the 'Publish state is left alone' note further scopes the behavior.

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?

The description implies usage by focusing on updating title/body, but it does not explicitly reference alternatives or provide when-to-use/when-not-to-use guidance. The publish state exclusion is a minor guideline, but no explicit contrast with create/get tools is given.

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