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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies read-only behavior, but the description does not disclose error behavior, unknown agent_id handling, access requirements, or whether the profile reflects the current agent or any agent. It only lists the returned fields.

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?

A single, front-loaded sentence with no wasted words. It states the action, resource, and key output fields efficiently, and every phrase contributes meaning.

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?

This is a simple getter with one fully documented parameter and no output schema, so the description's enumeration of the returned profile components (trust score, behavioral DNA, character model) is reasonably complete for invocation. It could go further by explaining value types or ranges, but for its low complexity the coverage is solid.

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 100% and the parameter includes useful examples ('oracle, spider, strategist'). The description adds little beyond the schema, but the schema already sufficiently explains the agent_id parameter, so baseline 3 is appropriate.

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 a specific verb ('Get') and resource ('agent identity profile'), and it names the contained fields (trust score, behavioral DNA, character model), making the purpose clear. It does not explicitly differentiate from sibling tools like soul_insights or soul_verify, but the resource is specific enough to be distinct.

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?

There is no guidance about when to use this tool versus its siblings, no explicit prerequisites, and no stated exclusions. The verb 'Get' implies a read operation, but the description does not help an agent choose between soul_profile and other soul_* tools.

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