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

Annotations only declare readOnlyHint=true; the description goes well beyond, defining the revision sentinel (0 = no such page yet), the 'problem' state meaning the page file is broken, and the resulting constraint that nothing can be saved until the user fixes or removes the file — plus an explicit instruction not to recreate the fields.

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-loads what the tool returns, then edge cases, then call-ordering rules; nearly every clause earns its place. The description is dense and somewhat run-on, packing return values, routing hints, and error semantics into a single block without clear separation.

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?

No output schema exists, so the description carries the return-value burden — and it does, enumerating the page settings, fields, tabs, and revision. It also covers the 'problem' failure mode and the ordering relative to save-options-page, leaving nothing an agent needs 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 coverage is 100% and the single slug parameter is fully documented in the schema (pattern, examples, character rules). The description adds no additional syntax or format detail for the parameter, so the baseline 3 applies.

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+resource (fetch one options page) and enumerates exactly what it returns: page settings (title, menu label, description, position, autoload), fields with names, tabs, and revision. It clearly distinguishes itself from list-options-pages, get-field-values, and save-options-page by scope.

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?

Explicit sequencing: call before save-options-page because you need the revision and existing fields, and before render code reads the page. It also names the correct alternative for values (get-field-values) and the prerequisite skill doc (options-contract) to read before the first call.

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