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

With readOnlyHint, idempotentHint, and destructiveHint already covering the safety profile, the description adds value by disclosing the auth requirement ('No account needed') — a fact absent from the annotations. It also frames the tool as a prerequisite discovery step, which no annotation conveys.

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?

Two short sentences, front-loaded with the payload enumeration followed by the two operational facts (no auth, use early). Every clause carries distinct information and nothing is redundant with the title.

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?

Return values are covered by the output schema, annotations cover the safety profile, and the tool has no inputs, so the description only needs to say what capability data is exposed and when to fetch it — both are present.

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 the baseline is 4; there is nothing for the description to disambiguate and the empty schema is self-evident. The description correctly avoids wasting words on non-existent inputs.

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 uses a specific verb ('Read') and a clearly scoped resource (MyReach publishing actions, editable fields, appearance choices, limits, restrictions), which tells an agent exactly what information it will get back. It is distinct from all siblings, which operate on pages, drafts, accounts, or publication status, though it never names an alternative explicitly.

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?

'Check before choosing a workflow' gives a concrete timing cue: call this first, then pick among the sibling page/publication tools. It stops short of naming which siblings this precedes or when to skip it, so it is clear context rather than full exclusions.

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