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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real behavioral context beyond them: live items and draft items are separate collections, hasUnpublishedDraft/draftItems surface queued work, and drafts only go live when the owner publishes in the app. It still omits ordering, completeness, and whether all pages or one account's pages are returned.

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 core action and return fields, then a second sentence for the draft/live nuance; no filler sentences. The field enumeration in the first sentence is dense and slightly list-like, but every element corresponds to real output data.

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 no output schema, no parameters, and a simple read-only surface, the description must explain what comes back — and it does, including the draft-vs-live split. What remains unstated is the ordering/paging of results and whether the list spans all pages in the account or a subset.

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 schema carries no semantics to supplement and the baseline is 4. The description appropriately spends its words on scope and return shape instead of parameters.

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 opens with a specific verb+resource ('List the Bio pages') and enumerates the returned fields (handle, public address, published flag, title, editUrl, items), which makes the tool's scope concrete. It never names a sibling, so the read-vs-write distinction against tools like add_to_bio_page must be inferred rather than stated.

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?

Usage is only implied: an agent can gather that this is the enumeration/read path for Bio pages, but there is no explicit 'use this when...' statement, no mention of alternatives, and no preconditions. Naming add_to_bio_page or get_link as the mutation/single-item counterparts would have raised this.

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