notion_bulk_property_update

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

Without annotations, the description carries the full burden. It mentions routing through the domain-agent dispatcher with JWT/tenant/scope, which provides some auth context, but does not disclose side effects, idempotency, or what the action actually modifies. Key behavioral traits are missing.

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 short (three sentences plus two parameter descriptions) and front-loaded with the action name. Every sentence provides some information, but the first sentence is somewhat redundant with the tool name. Overall efficient with minimal waste.

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 the tool's likely complexity (bulk update in Notion) and the presence of an output schema, the description fails to explain core functionality like which properties can be updated, scope (single page vs multiple), or limitations. Contextually incomplete for effective use.

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. The descriptions 'Free-text objective' and 'Optional JSON string' add some meaning beyond the schema's titles and defaults, but are vague and lack format or constraint details. Insufficient for precise invocation.

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 states it runs the 'bulk_property_update' action but does not explain what that action does in Notion context. It is slightly better than a tautology and distinguishes from sibling tools like notion_bulk_status_update by name only, but fails to convey the actual purpose.

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 other update tools (e.g., notion_update_page, notion_bulk_update_pages). The description lacks context about typical use cases, prerequisites, or alternatives.

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