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

Beyond the readOnlyHint=true annotation, the description discloses truncation behavior ('Long text blocks are truncated to a 300-character preview') and hard exclusions ('Never returns email-sync credentials or tracking pixel IDs'). It also states exactly which data is returned in full, giving the agent an accurate coverage model of the call.

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?

Four sentences, each earning its place: scope enumeration, parameter omission rule, truncation warning, and exclusion list. The purpose is front-loaded in the first phrase, with supporting detail ordered by importance.

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 a single optional parameter, a readOnlyHint annotation, and an output schema present, the description completes the picture: full return scope, truncation limit, and exclusions. Nothing an agent needs to invoke the tool correctly or predict its output 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 coverage is 0% and the bare schema exposes a single undocumented optional siteId, so the description must carry the meaning. It adds real value by stating when the parameter can be dropped ('Omit siteId when the team has exactly one site'), implying optionality and multi-site disambiguation. It stops short of explaining how to obtain a siteId via a sibling tool, but the guidance given is substantive.

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 leads with a specific verb+resource pair ('Read one bio page in full') and enumerates the precise return scope: profile header, social icons, every content block type, SEO metadata, theme and auto-pin settings. This scope clearly separates it from siblings like list_mini_sites (a list operation) and get_mini_site_analytics (metrics).

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 offers one explicit call-time rule: 'Omit siteId when the team has exactly one site.' However, it never names alternatives or states when another tool should be chosen instead—e.g., list_mini_sites for site discovery or get_mini_site_analytics for metrics. The credentials/pixel-ID exclusion is behavioral disclosure, not routing guidance, so choosing between siblings is left to inference.

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