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

With no annotations, the description carries the full burden and does well: it discloses the data source (team's own activity, 30-day window), the cost (free), and the absence of side effects ('executes no provider'). What it omits is auth/prerequisite behavior for an unconnected team and what an empty result looks like.

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 tight clauses, front-loaded with what is listed and scoped, then the client context and cost/safety note. No redundant restatement of the title or name.

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 no-parameter, no-output-schema read tool, the description covers provenance, scope, per-item reason, cost, and side effects. A brief note on return shape or empty-state behavior would close the remaining gap.

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 takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify beyond confirming no inputs are required. No contradiction with the empty schema.

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 and resource ('List data providers recommended') plus scope: the connected team's own Firecrawl activity over the last 30 days, each with a reason. The personalization language implicitly separates it from the generic firecrawl_provider_directory, though that sibling is never named outright.

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?

'Used by the Firecrawl sidebar' gives clear context for when this is appropriate, and 'free, and it executes no provider' signals the cost and safety profile an agent would want before calling. It stops short of explicitly contrasting with firecrawl_provider_directory or stating when not to use it.

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