add_lineage

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

The description is vague about behavior: it says 'add or update' but does not explain conflict resolution, idempotency, permissions, or side effects. No annotations are provided to fill the gap.

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 minimal (one sentence) but lacks necessary detail, making it under-specified rather than efficiently concise.

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?

The tool deals with a complex concept (lineage) but provides no output schema, no parameter structure, and no context on how to use the 'lineage_data' object. The agent has insufficient information.

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?

The single parameter 'lineage_data' is an opaque object with no schema details. Schema description coverage is 0%, and the description offers no hints about its structure or required fields.

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 states a specific action ('Add or update lineage between entities'), but it does not differentiate from sibling tools like 'get_lineage' or 'delete_lineage' beyond the obvious verb distinction.

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?

No guidance is provided on when to use this tool vs alternatives, such as when to add vs update lineage, or how it relates to other entity management tools.

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