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

With no annotations, the description carries the transparency burden. It discloses that only published profiles are returned and enumerates the returned fields, which is useful behavioral context. It does not discuss error cases, authentication, or rate limits, but for a simple read operation this is adequate.

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?

The description is a single, well-structured sentence that front-loads the core behavior and uses a colon to compactly list the returned profile components. There is no redundant or filler content.

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?

An output schema exists, so return-value details are covered elsewhere. The description adequately explains the lookup mechanism and scope for a simple fetch-one tool. Minor gaps remain around handling of nonexistent or unpublished handles, but they do not materially impair correct invocation.

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 clarifies that 'handle' is the lookup key, but adds no format, uniqueness, or case-sensitivity details. Since there is only one self-explanatory parameter, this is acceptable but not richly documented.

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 clearly identifies the operation as retrieving a single profile by handle and lists the profile contents returned (headline, bio, work history, etc.). The title 'Read one profile' plus 'One published profile by handle' distinguishes it from the search_people and other get_* siblings.

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 phrase 'One published profile by handle' gives clear context: use this when you have a specific handle and want that profile's details. It does not explicitly state when to prefer search_people or other alternatives, but the access pattern is obvious enough to guide selection.

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