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

With no annotations, the description carries the full burden of behavioral disclosure. It communicates a read-oriented action via 'Get' and previews the output facets, which is useful context. However, it does not disclose permission requirements, error behavior, or what 'behavioral DNA' and 'character model' concretely contain.

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 sentence that starts with the action and packs in the resource and return facets. There is no filler, and the em-dash structure keeps the purpose front-loaded without sacrificing detail.

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 one-required-parameter read tool, the definition is nearly complete: the call contract is clear and the expected output areas are named. The lack of an output schema leaves return-structure details slightly underspecified, which prevents a perfect score.

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 only parameter, agent_id, is fully documented in the schema with example values, and schema description coverage is 100%. The description adds no parameter-level guidance, so the baseline score of 3 applies.

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 names a concrete operation ('Get') and a specific resource ('agent identity profile'), and enumerates the returned dimensions (trust score, behavioral DNA, character model). It does not explicitly differentiate from sibling tools like soul_insights or soul_verify, so it misses the top score.

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 implies a clear use case—use this when you need an agent's identity profile—but it never states when not to use it or names a sibling alternative. The usage guidance is implicit rather than explicit.

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