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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description doesn't need to. It adds genuine context beyond them: the dependency chain on search_events for event_id and what each action yields (presets grouped by category, a section's blocks and styles). Rate limits and error behavior are unaddressed, keeping it below a 5.

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?

Front-loaded with a one-line purpose, then a scannable bullet per action, then the prerequisite. Every sentence carries either an action contract or a dependency; nothing is padded.

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?

With an output schema present, return-shape detail is optional, and the description covers all three action contracts plus the event_id dependency. The remaining gap is positioning against neighboring site tools (read_site, read_site_pages, add_site_section_preset) for an agent choosing where to start.

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 coverage is 100% and the oneOf branches already enforce which parameters each action requires, so the description largely restates the schema. It adds modest value by tying required params to actions in prose and clarifying that block_type selects which block schema is returned. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb and resource set — reads section presets plus section and block schemas for the registration site — and enumerates the three actions it performs. An agent can distinguish this from read_site, read_site_pages, and add_site_section_preset without opening any schema.

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 action dispatch gives clear per-action contexts: list presets, fetch one section with blocks and styles, fetch a block's JSON schema. The prerequisite 'event_id must be the event UUID returned by search_events' routes the agent to the right upstream tool. It stops short of naming when to prefer read_site_pages or read_site instead, so no explicit exclusions.

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