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

With no annotations, the description carries the full burden and responds well: it discloses per-call cost (0.011000 USDC), that null means unknown, that a summary/header is not the underlying record list, that additional pages require separate requests, and that there is no completeness/safety guarantee. This is meaningful operational context beyond the schema.

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?

The purpose is front-loaded, which is good. But the remainder is a run-on block of disclaimers with redundancy — 'No ... completeness ... safety certification' and 'No completeness or safety guarantee' restate the same caveat, padding the definition.

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 count tool with a single opaque parameter and no output schema, the description covers the essentials an agent needs: what it returns (a count, not a list), where to get the identifier, pricing, and pagination behavior. Only the count-vs-overview routing and exact argument fields 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 coverage is 0% and the single parameter is an opaque 'arguments' object with additionalProperties, so the schema conveys almost nothing. The description partially compensates by naming the company_id source and pointing to get_cn_data_tool_schema for the real argument contract, but it does not spell out the required fields itself.

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+resource: querying the overall count of enterprise qualification certificates. Clear enough for an agent to know what comes back (a count). However, it does not explicitly differentiate itself from the sibling cn_data_v3_certificate_overview, leaving the count-vs-overview distinction to inference.

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?

Provides actionable sourcing guidance: use company_id from cn_data_v3_company_detail and pass arguments matching get_cn_data_tool_schema("v3_certificate_count"). But it never states when to choose this count tool over certificate_overview or the other *_count siblings, so alternative selection is only implied.

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