retrieve_entity_snapshot

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

The description indicates a read operation (retrieve) and mentions provenance and historical support, but lacks details on side effects, permissions, or return behavior. With no annotations, the description carries the full burden and is adequate but not rich.

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?

Two sentences, no wasted words. Front-loaded with main action, then adds key feature. Each sentence earns its place.

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 tool has 3 parameters, no output schema, and no annotations, the description is mildly inadequate. It does not explain what 'provenance information' entails, what the response looks like, or clarify the entity_id parameter. More context would help agent use correctly.

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 67%; the description adds no new information beyond what's in the schema. The 'at' parameter's historical usage is already documented in the schema, and entity_id remains undescribed. Baseline of 3 is appropriate as schema does most of the work.

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 it retrieves a snapshot of an entity with provenance, distinguishing it from sibling tools like retrieve_entity_by_identifier or retrieve_entities. The mention of historical snapshots via 'at' parameter adds specificity.

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 historical queries via 'at', but does not explicitly state when to use this tool over alternatives or provide any exclusion criteria. No comparison to siblings is given.

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