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 discloses that the tool returns counts plus recent samples and explains family rolling behavior, but lacks details on authorization, rate limits, data freshness, or potential performance impact.

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 four sentences, well-structured with the purpose first, followed by content summary, a value statement, and a usage hint. It is efficient and front-loaded.

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?

Given the complexity and number of sibling tools, the description sufficiently covers what the tool returns and how to use its parameters. It lacks output schema details but indicates 'counts plus recent samples' which is adequate.

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 schema already documents parameters. The description adds value by explaining the effect of include_family ('roll the totals up'), but does not elaborate on family_confidence or include_subsidiaries beyond what the schema provides.

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 returns a 'cross-source dossier for an entity (by UUID)' and enumerates the data types included, distinguishing it from sibling tools like get_entity_profile by calling it 'the most complete single view'.

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 explains when to use the tool (for a comprehensive single view) and provides guidance for the include_family parameter, but does not explicitly contrast with alternatives like get_entity_profile or mention when not to use this tool.

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