get_agent_profile

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

No annotations are provided, so the description must disclose behavior. The use of 'Retrieve' implies a read-only operation, and the mention of 'identity and permissions' hints at the data scope. However, it does not explicitly state that the operation is non-destructive, nor does it describe error handling, authorization requirements, or side effects.

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 front-loaded with a clear one-sentence purpose, followed by a focused WHEN TO USE list. Each bullet is concise and relevant, with no filler or redundant 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?

The tool is simple with a single parameter and no output schema, but the description does not specify what fields constitute 'detailed profile information' or the return shape. The scenarios are helpful for context, but the absence of return details leaves a gap given no output schema exists.

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 input schema already fully documents agent_id with 100% coverage, including the source from register_agent(). The description adds no meaningful parameter-specific details beyond the schema, so it meets the baseline for schema-covered parameters.

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 uses the specific verb 'Retrieve' with the resource 'detailed profile information about a specific agent', which clearly states the tool's function. It distinguishes from sibling list tools like get_agents_list by emphasizing 'specific agent'.

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 WHEN TO USE section explicitly lists four appropriate scenarios, such as checking registration details, understanding another agent's work, verifying identity and permissions, and coordinating between agents. However, it does not mention alternatives or when not to use, so it provides clear context but no exclusions.

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