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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the trailing 'Read-only.' mostly restates structured data. The description earns credit instead by disclosing what observable data comes back (public state, link, self-description, question count), which tells the agent this is a profile-read rather than a state mutation or content-generation 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?

A single sentence, front-loaded with the usage trigger before the content list, with no filler. It runs slightly long as a comma-chained list, but every clause maps to a genuine aspect of the response.

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 parameterless read tool with an output schema and full annotation coverage, the description supplies exactly what structured fields cannot: the intent that should select it and the shape of what it reports. Nothing an agent needs in order to call it correctly 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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description appropriately spends its words on scope and returned content instead of inventing parameter detail.

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?

Specific verb (get) plus a precisely scoped resource (the user's own AI clone) and an enumeration of the fields returned: public status, link, self-description, and visitor question count. The word 'own' distinguishes it from sibling tools that act on other people's clones, so an agent can pick it without opening the schema.

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?

Explicitly anchors invocation to a trigger: 'when the user asks about their own AI clone.' This gives clear context for when to call it, but it names no alternatives or exclusions (e.g., that visitor questions themselves come from list_visitor_questions), so routing for adjacent intents is left partly to inference.

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