API-patch-page

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It mentions 'Update' which implies mutation, but doesn't disclose permission requirements, whether changes are reversible, rate limits, or what happens when properties are omitted. The schema reveals additional behaviors like archiving and trash management that aren't mentioned.

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 extremely concise with just two words plus context. Every word earns its place - 'Notion' provides context, 'Update' specifies the action, and 'page properties' identifies the resource. No wasted words or redundancy.

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 6 parameters, no annotations, and no output schema, this description is inadequate. It doesn't explain what successful updates return, error conditions, or the scope of changes possible. The schema reveals complex nested structures for properties, cover, and icon that aren't hinted at in the description.

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?

With 83% schema description coverage, the schema does most of the parameter documentation work. The description adds no specific parameter information beyond the generic 'page properties' mention. It doesn't explain what 'properties' means in the Notion context or clarify the relationship between different parameter groups.

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 the action ('Update') and resource ('page properties') with the Notion context. It distinguishes this as a modification tool rather than creation or retrieval, though it doesn't explicitly differentiate from similar update tools like 'API-update-a-block' or 'API-update-a-database'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites like needing a page ID, when to use this versus 'API-patch-block-children' for content updates, or what constitutes appropriate 'page properties' to modify.

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