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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuinely useful behavioral context, sort order and the presence of lead counts per progress stage, but says nothing about pagination, result limits, or the shape of the response.

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 terse sentences with no filler, and the ordering/output detail is front-loaded right after the core statement. The phrasing is fragmentary but every clause carries information not available in the structured fields.

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 output schema, the description usefully signals that results are sorted newest-first and include lead counts. However, for a list endpoint it omits the status filter explanation, pagination/limit behavior, and what an omitted status means, so an agent cannot determine the default result set.

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 the description never mentions the one available parameter, an array-based status filter accepting draft/running/paused/completed. The description therefore does not compensate for the coverage gap, leaving the filter's semantics (multi-value OR filtering vs. something else) undocumented in both places.

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 verb and resource ("List campaigns") and adds scope detail with result ordering and included aggregates ("Newest first, with lead counts by progress"). It does not, however, differentiate itself from siblings like get_campaign or list_leads, so the reader must infer the distinction.

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 when-to-use guidance, no mention of prerequisites, and no naming of alternatives such as get_campaign for a single campaign. The only hint at a filter is the undocumented status parameter, so usage must be inferred entirely from the schema.

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