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's job is to add context — and it does by disclosing exactly which page facets come back, which matters because there is no output schema. It stops short of describing response shape or ordering, but with annotations carrying safety that is a minor gap.

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 the verb and resource, then a single dense enumeration sentence, closing with the imperative usage cue. The facet list is long but each item is a real returned field, so it earns its space given the absence of an output schema; it is slightly list-heavy rather than wasteful.

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 zero-parameter read of a composite page object, everything an agent needs is present: what is read, which facets are included, and when to reach for it. With no output schema, the facet enumeration effectively stands in for a return-value description, and the annotations cover side-effect questions.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly spends no words on parameter semantics and devotes its space to what the call returns instead.

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 (read) and a specific resource (the user's public Achriom page setup), then enumerates the exact facets returned: address, style components, headline, Currently lines, rating names, My 9s, pins, hidden sections. This clearly separates it from the many adjacent setters (style_page, set_headline, set_hidden, set_page_sections) because it is the read-side counterpart that returns all of them at once.

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?

Gives an explicit calling condition: read this before changing the page, which positions it as the prerequisite read for the whole set_*/style_* family. It does not name a specific alternative or state when-not to use it, but the read-before-write framing is concrete enough to drive selection.

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