retrieve_entity_snapshot

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions 'provenance information' but does not state whether the operation is read-only, any side effects, prerequisites, or error handling (e.g., missing entity). This leaves significant gaps for safe invocation.

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 two sentences, front-loads the core purpose, and every word adds value. No fluff or redundancy.

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 retrieval tool with no output schema, the description should clarify what the snapshot contains (beyond 'provenance information'). It also lacks notes on response format defaults or pagination. While adequate for a simple tool, it leaves minor gaps in completeness.

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 description coverage is 67%, and the description adds context for the 'at' parameter (historical snapshots). The 'format' parameter is well-documented in the schema. However, 'entity_id' is undocumented in both schema and description, and its optionality is not explained. The description adds some value but does not fully compensate for gaps.

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 action ('Retrieve'), the resource ('current snapshot of an entity'), and adds context about provenance information and historical support via the 'at' parameter. This differentiates it from sibling tools like 'retrieve_entities' and 'retrieve_entity_by_identifier' which deal with entities rather than snapshots.

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 for snapshot retrieval and mentions historical snapshots, but does not explicitly guide the agent on when to use this tool versus alternatives (e.g., for current entity state vs historical). No exclusions or when-not-to-use are provided.

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