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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard cap of 50 results and confidence-descending ordering. It omits what happens when truncation occurs or how to fetch more, which keeps it from a 5.

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?

Front-loads the key return semantics in the first sentence and follows with a compact Args block. No filler; the only mild redundancy is restating entity_id in the args list, though it usefully carries the UUID format 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 one-parameter read-only tool with full annotation coverage and no output schema, the description covers scope, result cap, ordering, and parameter format. The main gap is truncation/pagination behavior when the 50-result cap is hit.

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 0% and the only param is a bare string, but the description compensates by specifying the expected format ("UUID of the entity"), which the schema does not convey. With a single fully-described parameter, this is adequate.

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?

States a specific verb+resource ("Get semantic facts") plus the scope ("in which an entity is the subject or the object"), which is more precise than the title. It does not name or distinguish itself from plausible siblings like get_entity_relations or get_entity_episodes, so it stops short of full sibling differentiation.

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 says what is returned but never states when to choose this tool over alternatives such as get_entity_relations, get_entity_neighbors, or query_world_model. No prerequisites, exclusions, or usage context are given; the agent must infer usage from the name.

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