invalidate_entity

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

Describes key behaviors: idempotent, no deletion, entity_as_of still returns past timestamps. With no annotations, this description fully informs the agent of the tool's effects.

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?

Three concise sentences with no fluff. Each sentence adds distinct value: purpose, idempotence/non-deletion, orthogonality to supersession.

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 simple tool with two params and no output schema, the description covers all necessary behavioral aspects. No gaps identified.

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 100%, baseline applies. Description does not add parameter-specific details beyond schema; mentions setting validUntil but doesn't elaborate on 'ended' 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?

Description clearly states the tool marks an entity as invalid by setting validUntil. It specifies the verb 'mark' and resource 'entity', and differentiates from deletion and supersession among many siblings.

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?

Implicitly guides usage by stating idempotence and non-deletion behavior, contrasting with supersession. Lacks explicit 'when to use' or 'alternatives' but context from siblings is leveraged.

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