hebbrix_entity_timeline

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

No annotations provided, so description bears full burden. Discloses bi-temporal nature and that it returns factual history. However, does not mention auth requirements, rate limits, or any side effects (likely read-only, but not stated). Could be more explicit about safety.

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, zero wasted words. Front-loaded with core purpose ('Bi-temporal timeline for one entity') followed by usage scenario. Perfect conciseness.

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?

Has output schema, so return values need not be detailed. Description covers what it does (entity timeline with bi-temporal facts) and when to use it. Could mention scope (single entity) and temporal aspects, but overall complete for a simple tool.

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 0% for 2 parameters. Description does not explain either parameter (entity_name is self-explanatory, collection_id is not described). Although schema has titles, the description adds no value beyond the schema. With 0% coverage, description should compensate, but it does not.

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?

Clear verb-resource: 'Bi-temporal timeline for one entity: what facts were true about it and when.' Distinguishes from siblings like hebbrix_history (which likely shows all changes) and hebbrix_search (which searches across entities).

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?

Explicitly states use case: 'for "what changed" / "what was true at time X" questions about a person, company, or thing.' Lacks when-not-to-use or alternatives, but the guidance is clear and actionable.

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