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

With no annotations, the description itself communicates that this is a non-mutating introspection call by describing exactly what information it returns. It does not discuss errors, latency, or response format, but the zero-parameter read-only nature is sufficiently implied.

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 sentence packs the output contents and the primary usage instruction with no filler. The most important operational guidance ('Call this first') remains direct and unambiguous.

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 zero-parameter schema-introspection tool with no output schema, the description covers what an agent needs: what the call returns and when to call it. No missing prerequisites or side effects are needed to invoke it correctly.

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 tool has no parameters, so the description cannot add parameter-level meaning; baseline 4 applies. It still clarifies what the returned schema information will contain, which is the relevant semantic context.

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 the exact resource (Funnelvo dataset) and enumerates the returned content: columns, numeric flags, row count, and provenance banner. It also states a clear invocation role ('Call this first to learn the schema'), which visibly separates it from the sibling analysis 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?

'Call this first' is an explicit usage directive for agents starting to understand the dataset. It gives a clear context for use, though it does not spell out when not to use it or name alternatives.

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