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

The readOnlyHint annotation already declares the safety profile, but the description adds a genuinely useful fact the annotation cannot convey: the underlying Castle call is a POST, so an agent should not infer a mutation from the HTTP verb. It also names the concrete endpoint. No return format or pagination notes, but those matter little for a 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 sentences, front-loaded with the purpose and scoping, followed by the read-only clarification and endpoint. Nothing is padded.

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 count tool with no output schema there is little else an agent needs: it knows what is counted, on which list, with which filters, and that the call is safe. The only residual gap is that filter operator semantics are deferred to the sibling search tool rather than spelled out.

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%, so list_id and filters are already documented in the schema. The description's note that filters mirror "the search" adds marginal routing value but no new syntax or field/op semantics beyond the schema. Baseline 3 applies.

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 (count) and resource (entries in one list), and implicitly contrasts with the sibling that returns items rather than a count. An agent can distinguish this from castle_search_list_items without opening either schema.

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?

"with the same optional filters as the search" implies when this is used (you want a count, not the item payloads), but there is no explicit when-to-use guidance or named alternative such as castle_search_list_items. Usage is implied rather than stated.

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