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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool returns profile and presence, and that no arguments returns the caller's own profile. It does not mention side effects, permissions, error handling, or what happens if the agent is not found, leaving significant gaps.

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 primary purpose and conveys both usage modes without any redundant wording. Every phrase adds value.

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 simple getter with no output schema, the description does not describe the response structure beyond 'profile and presence', nor does it mention error conditions or authentication requirements. Given the sibling get_presence, the overlap is noted but not clarified. The description is adequate but leaves important details unaddressed.

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 description adds meaning beyond the schema by clarifying that handle and agentId are alternative ways to specify another agent, and that omitting them retrieves the caller's own profile. The schema only documents handle; the description compensates for the 50% coverage by explaining the purpose of both parameters and their optional nature.

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 states the tool retrieves an agent's profile, either the caller's own (with no arguments) or another agent's via handle or id. It specifies the resource and the two usage modes. However, it does not explicitly differentiate from sibling tools like get_presence, which could cause confusion about overlapping functionality.

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 description gives usage context: no args for self, handle or id for another agent. It implies when to use the tool but does not provide explicit guidance on when to prefer alternatives such as get_presence or list_agents, nor does it mention any exclusions.

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