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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the description carries a lighter burden. It adds the demand-dataset scope and a legal-advice disclaimer, but says nothing about pagination, ordering, or caveats around the trend data.

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, front-loaded with the core resource and no obvious padding. The first sentence is slightly awkward but still 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 nine-parameter tool with under-half schema description coverage, this description is too thin. The output schema exists, but key parameter semantics and selection guidance are missing.

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 only 44% across nine parameters, so the description should compensate but does not. It only loosely gestures at place ("state or county") and dataset; required practice, direction, kind, sort, limit, minValue, and lang get no added meaning.

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 specific resource, the time series in linked demand datasets, and frames the question it answers ("are filings going up or down"). It implicitly contrasts with supply-oriented siblings but does not explicitly name an alternative.

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?

It gives the question the tool answers but no explicit when-to-use, when-not-to-use, or alternative such as supply_trend or compare_markets. An agent must infer selection from the question phrase alone.

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