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

The description goes well beyond the annotations. It discloses a non-obvious side effect: 'Counts as a page view (agents are genuine visitors).' This is critical behavioral information that an agent would not infer from readOnlyHint=true. It also states 'Public, no auth,' which sets expectations about access requirements. The description adds meaningful behavioral context beyond what annotations provide.

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?

Three sentences, each earning its place: the first defines the resource and its contents, the second discloses the side effect, the third states access requirements. The most important scoping information is front-loaded. No wasted words.

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 single-parameter read tool with readOnlyHint=true and destructiveHint=false, the description is complete. It covers what the page contains, the side effect of viewing, and the auth requirement. There is no output schema, but the enumerated content list gives the agent a clear picture of what to expect in the return value. Nothing essential is missing.

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 description coverage is 0%, so the description must compensate. It explains that 'handle' is the builder's handle used to render the page, and the parenthetical '(what /@handle renders)' gives the format. It doesn't specify whether the handle needs a leading @ or exact casing, but for a single-parameter tool with this level of context, the description provides adequate semantic grounding.

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 states a specific verb ('Read'), a specific resource ('a builder's public page'), and the exact lookup key ('by handle'). It enumerates the page contents (profile, links, badge, public creations, activity heartbeat, view counts, rig sub-pages), which distinguishes it from sibling tools like page_me, page_directory, and page_leaderboard. The parenthetical '(what /@handle renders)' grounds it in concrete user-facing behavior.

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 description clearly implies when to use this tool: when you need a builder's public page by handle. It does not explicitly name alternatives or exclusions, but the sibling list contains page_me, page_directory, and page_leaderboard, and the description's focus on a single handle's public page makes the usage context clear. It lacks an explicit 'use X instead when...' statement, so it doesn't reach a 5.

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