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

readOnlyHint=true already establishes the safe-read profile, and the description adds useful context by naming the underlying aggregation (GET /query with count(*)), confirming it is a server-side count rather than a fetch-and-tally. It says nothing about limits on filter combinations beyond the schema's maxItems or about the response value being a plain count.

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 short clauses with the purpose front-loaded and zero padding; the endpoint detail is compact and contributes transparency rather than noise. Nothing in it is wasted, though it is terse to the point of under-specifying usage.

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 two-parameter read-only count tool with full schema coverage, no output schema, and a readOnlyHint annotation, the description covers what the tool does and how filters relate to the sibling tool. The only real gap is that it doesn't state that the return value is a simple integer count, which an agent could otherwise assume wrongly.

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 100% and documents module names, the operator enum, AND combination, and the maxItems cap, so the schema carries the semantic load. The description's only added value is cross-referencing the filter syntax to vtiger_list_records, which is helpful but marginal.

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 operation (count records of a module) and explicitly ties its filter semantics to the sibling vtiger_list_records, so an agent can tell it apart from the listing tool. The phrasing is slightly indirect ('How many records...') but still unambiguous about the verb and resource.

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?

The reference to 'same filters as vtiger_list_records' implies this is the counting counterpart to listing, but the description never says explicitly when to use it over vtiger_list_records (e.g. 'use when you only need a count, not the rows'). Usage is inferable rather than stated.

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