sovereign_get_entity_dossier

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

No annotations are provided, so the description carries the full burden. It does disclose the read-oriented nature of the operation ('compiles'), the content categories, and the 1–5 hop traversal. However, it does not mention whether the tool has side effects, how expensive deep traversal is, or how entity vs entity_name are resolved when both are supplied.

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 entire description is one dense, front-loaded sentence. It states the main purpose first, then lists the key content categories without repetition or filler. Every phrase earns its place.

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 tool with no output schema and no annotations, the description gives a reasonable sense of the returned content, but it omits important operational details: there are zero required parameters, yet the tool is for 'an entity,' and the description does not explain what happens if no entity is provided or how the two entity parameters interact. Usage context is also left implicit.

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 coverage is 100%, so the baseline is 3. The description reinforces the 'hops' semantics by mentioning multi-hop cross-references, but it does not add meaningful detail beyond the schema, such as precedence between entity and entity_name or fuzzy matching behavior.

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 ('compiles') and resource ('relational knowledge graph dossier for an entity'), and enumerates concrete outputs: linked documents, timeline, transactions, and multi-hop cross-references. This clearly differentiates it from siblings like sovereign_search_vault or sovereign_node_status.

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 explicit guidance on when to use this tool versus alternatives, nor any stated exclusions or routing conditions. The word 'complete' implies comprehensive investigation, but the description does not tell the agent when to prefer this over sovereign_search_vault or sovereign_route_and_analyze.

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