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

No annotations are provided, so the description carries the entire behavioral burden, and it discloses nothing: not whether the call is read-only or mutating, what a chain-integrity check verifies, whether it consumes a registered model, or what authorization or cost it implies. A bracketed category tag is not behavioral disclosure.

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?

It is short, but this is under-specification rather than conciseness — nothing useful is front-loaded because nothing useful is stated at all. The fragment is only a category label plus a code.

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?

With no annotations, no output schema, and two required parameters at 0% coverage (one being an untyped object array), the description is completely inadequate for invoking the tool correctly. An agent could not construct a valid, meaningful call from this text.

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 description coverage is 0% and both parameters are required, yet the description never mentions model_id or dataset_stages. The array-of-untyped-objects parameter is especially opaque, and the description adds zero syntax, format, or structural meaning beyond the raw schema types.

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 names a resource category ('Data lineage') but supplies no verb and no statement of what the tool actually does with lineage data. The internal tag '(LIN-100-ChainIntegrity)' is a control identifier, not an explanation, and it does nothing to distinguish this tool from ~15 sibling compliance_* and audit_* tools.

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?

There is no guidance on when to use this tool, when not to, or which sibling (compliance_check, compliance_explain, compliance_eu_ai_act, drift_certificate, etc.) it should be preferred over. An agent has no basis for routing between these tools.

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