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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful data-scope constraints ('Metadata/approved fields only; no secrets, contacts or original files'), which goes beyond annotations. However, it does not disclose return format, pagination behavior, or authorization requirements in detail.

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 sentences with the data-scope constraint front-loaded. 'Through the existing application' is minor filler, but otherwise the description is 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 simple count tool with no output schema and fully undocumented parameters, the description should at least clarify what is being counted and how the query/limit/offset operate. It leaves these essentials unspecified.

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% for all three parameters (limit, query, offset), and the description provides no information about their meaning, defaults, or usage. It completely fails to compensate for the undocumented parameters.

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 states a specific verb and resource ('Read authorised pending ce count'), but 'ce' is an unexplained abbreviation and the phrasing is vague. It implicitly distinguishes a count from list-style siblings like list_pending_ce_submissions by saying 'count', though it never names or contrasts with them.

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 guidance on when to use this tool versus alternatives such as list_pending_ce_submissions or get_pending_ce_count-like siblings. 'Through the existing application' does not clarify usage conditions or exclusions.

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