entity_predecessors

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

No annotations present, so description carries full burden. It discloses the exact fields returned and the focus on the transition leading to the entity. Does not mention side effects or permissions, but as a read operation this is sufficient.

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 with no wasted words. First sentence defines output fields, second provides a practical example. Highly efficient.

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 one parameter and no output schema, the description explains what is returned and gives a usage example. Lacks discussion of edge cases (e.g., no predecessor), but overall informative and sufficient.

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?

Only one parameter (entity_id) with numeric type. Description adds meaning by indicating it refers to a historical entity (e.g., 'Repubblica di Turchia'). Schema coverage is 0% but the implicit context helps. Does not explicitly document parameter meaning, so baseline 3 is appropriate.

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 returns predecessor chains with specific fields (immediate predecessor, transition_year, transition_type, is_violent, ethical_notes). Provides a concrete query example, distinguishing it from sibling tool 'entity_successors'.

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?

Explicit usage example given: 'che entità ha preceduto la Repubblica di Turchia?'. No explicit when-not-to-use or alternative tools, but context is clear.

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