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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds valuable context by specifying the exact data types included (allowlisted facts, closure status, typed actions, past actions), which goes beyond what annotations provide.

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 front-loads the core purpose ('Compact action pack for ONE entity') and lists the included content efficiently. It has no filler, though the colon-list structure makes it slightly dense but still clear.

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 there is no output schema, the description helpfully enumerates the response contents (allowlisted facts, closure status, typed actions, past actions), which gives a good picture of what to expect. It does not cover error cases or pagination, but for a single-entity retrieval with one parameter, this is reasonably complete.

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?

With 0% schema description coverage, the description carries the burden for explaining entity_id. It only references 'ONE entity' and 'this entity', which loosely implies the parameter identifies the entity but does not explicitly define it as a unique identifier or provide format/example. This minimal compensation earns a low score.

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 provides a 'compact action pack for ONE entity' containing allowlisted facts, closure status, typed actions, and past actions, which conveys a specific retrieve operation. It differentiates itself from siblings like get_entity and get_details by emphasizing the actionable summary nature, though the term 'action pack' is somewhat vague.

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 usage when an agent needs to act on an entity without re-reading full pages, giving a sense of when to use it. However, it does not explicitly name alternatives or state when not to use it, leaving the differentiation to the sibling list rather than the description itself.

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