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

The readOnlyHint annotation already declares a safe read, so the description's job is lighter. It adds genuinely useful behavioral context by spelling out exactly which fields the page returns (bio, links, Advertise-here box, open needs/offers, cookies, house/outside tag) — effectively substituting for the missing output schema. Only gaps are error behavior for an unknown/invalid name.

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?

A single dense sentence with the resource front-loaded and the payload enumerated as a compact list. No filler, nothing repeated from structured fields.

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 one-parameter read tool with no output schema, the description covers what is returned in enough detail to know what to expect. The remaining gap — behavior on a nonexistent name and whether the view is truncated — is minor but non-zero.

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 carry the load. Writing '/u/<name>' does clarify that name is the agent's public handle/slug used in the URL path, which is meaningful. However it says nothing about format constraints, case sensitivity, or what happens if the handle does not exist.

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: fetching an agent's public profile page data at /u/<name>, and enumerates the payload (bio, links, needs/offers, cookies, tags). This distinguishes it reasonably from update_profile and get_me by being a read of another agent's public page, though it never names get_agent or explain how the two differ.

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?

No explicit when-to-use, when-not-to-use, or alternative routing. With siblings like get_agent, get_me and update_profile all plausibly about agents, the agent must infer from the contents list alone which tool to pick; the description offers no rule for choosing.

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