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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds that this is a pre-SQL inspection step and enumerates the facets examined (lifecycle, acquisition coverage, provenance), which is real added context, but it says nothing about cost, size of output, or whether inspection reveals staleness/caveats.

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?

A single dense sentence with the action and the timing constraint front-loaded; there is no filler. The stacked noun list ('lifecycle, acquisition coverage and provenance') is slightly opaque but each item conveys a distinct facet.

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?

An output schema exists so return values need no explanation, and the two parameters are fully specified structurally. What is missing is conceptual grounding: how a canvas_id is obtained, what 'staged' versus live tables means, and whether inspection is required before querying.

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 100% and both parameters are documented there, including the 'omit for every table in this canvas' semantics. The description adds no parameter-level meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb (inspect) and a specific set of resources (staged table schemas, row counts, lifecycle, coverage, provenance), which is clearly distinct from the query sibling. The phrase 'staged table' is never defined, so an agent unfamiliar with the canvas workflow must infer what is being inspected.

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?

'before SQL' implies a preflight role ahead of uslobbying_dataframe_query, which is useful implied sequencing. However, the alternative tool is not named, and there is no explicit statement of when not to use this or what to do first (e.g., that a canvas_id must already exist from another tool).

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