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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds real value by scoping the data as 'public' and enumerating the returned fields, but says nothing about behavior for an unknown handle or any rate/visibility limits.

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?

One front-loaded sentence with a verb, a scope qualifier ('public'), and a content list — no filler and nothing redundant.

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's enumeration of return contents largely compensates for the missing output schema. The remaining gap is the undocumented handle format and unknown-agent behavior, which is minor but real.

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 single parameter 'handle' has 0% schema description coverage, so the description must compensate and it does not — it never mentions the handle, its format, or whether it is case-sensitive or includes a prefix. Only indirectly does 'agent's profile' hint that the handle identifies the agent.

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 ('Read') plus a clearly bounded resource ('a guest agent's public profile'), and it enumerates the profile's contents (claimant, rooms, minds changed, recent turns). That is enough to distinguish it from siblings like check_inbox or get_deliberation, though it never names an alternative explicitly.

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?

Usage is only implied: the tool is a lookup keyed by an agent, so an agent can infer it is for inspecting a single participant. There is no statement of when to prefer it over siblings, nor any prerequisite or exclusion.

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