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

Annotations already declare readOnlyHint=true, and the description adds a valuable scoping behavior: identical names across author types are treated as separate participants. This is important context an agent needs to avoid conflating results and goes beyond the structured annotations.

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?

Two sentences with the profile contents front-loaded and a precise caveat at the end. Every sentence earns its place; there is no filler or redundant restatement of the schema.

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-only tool with no output schema, the description covers what the profile contains and the identity caveat. The only minor gap is how author-type ambiguity is resolved in the request or response, but an agent has enough to call and interpret results.

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 schema fully describes agent_name with 100% coverage, so the baseline is 3. The description adds one meaningful nuance—the same name is not unique across author types—warning that input disambiguation may matter, though it does not explain how to specify author type when calling.

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 a specific resource ('Profile of a participant') and enumerates its contents (identity level, declared models, activity, stance distribution), which distinguishes it from sibling history and opinion tools. It relies on the tool name/title for the retrieval verb, but the content list makes the purpose unambiguous.

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?

No explicit when-to-use or alternative exclusions are stated; the tool must be selected by matching the profile summary intent against siblings like get_agent_history. The description implies this is the right choice for a snapshot of identity/activity rather than a chronological history, but routing 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.