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

With no annotations, the description must carry the behavioral load. 'Read' implies a non-mutating operation and the description names the main returned artifacts, but it omits permission/auth requirements, failure behavior, pagination or truncation, and whether all three artifacts are always returned.

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 front-loaded sentence with no filler. It states the operation and the returned artifacts immediately.

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 read tool with no annotations and no output schema, naming the Entity Document, Identity Anchor, and last record entries is useful but minimal. It does not explain response shape, how the entries limit affects output, or authentication requirements beyond the required eid parameter in the schema.

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 50%: eid is described in the schema, while entries only has type/default/min/max. The description's phrase 'last record entries' hints that entries relate to recent records, but it does not explain the count semantics, default 10, or 100 maximum for the entries parameter.

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 gives a specific verb, 'Read', and a specific resource set: the caller's own Entity Document, Identity Anchor, and last record entries. 'Your own' scopes the operation to self, but it does not explicitly contrast with siblings such as openentity_read or openentity_find.

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 phrase 'your own' implies the tool is for inspecting the caller's own entity rather than another entity, which gives some usage context. However, it does not state when to choose this over openentity_read, openentity_find, or openentity_resolve, nor does it give exclusions or prerequisites.

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