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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool returns both a parsed view and the raw OpenProfile.md, which is useful output context, but it does not mention read-only nature, auth requirements, error behavior, or what happens when the profile is missing.

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?

It is very short and has no wasted words, with the identifier forms and return artifacts front-loaded. However, the fragmentary phrasing is less clear than a complete sentence and the colon introduces output details after a noun phrase.

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 low-complexity single-parameter read tool, the description covers the accepted refs and return artifacts. It still leaves gaps around behavior when the profile is not found, permissions, and when to prefer search_profiles, so it is adequate but not complete.

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 100%, so the parameter is already documented. The description adds the example format `<slug>-<id>` and repeats the handle option, but it does not add syntax rules, validation constraints, or lookup semantics beyond what the schema provides.

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 identifies the resource (one person profile) and the accepted identifier forms, and states that it returns a parsed view plus the served OpenProfile.md. It distinguishes exact lookup from sibling search_profiles implicitly, but lacks an explicit verb such as 'get' or 'fetch'.

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?

It lists valid reference formats but gives no when-to-use guidance, no explicit alternative to search_profiles, and no exclusions or prerequisites. An agent can infer exact-lookup usage, but the description does not state it.

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