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 covered. The description adds genuine behavioral value by disclosing the aggregation dimensions and the efficiency characteristic (avoids downloading the full list), which matters for large cadences. It does not mention the admin-only constraint on target_user_id (left to the schema) or any rate limits.

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 compact sentences with the category label and the core capability front-loaded before the use cases. The emoji section header is mild noise but does aid scanning, and no sentence is redundant.

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?

There is no output schema, but the description compensates by indicating the return shape (counts grouped by status and by current step). For a two-optional-parameter read-only count tool this covers what an agent needs, with only the response field names left 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 100%, so both parameters are already documented in the schema, including the admin-only restriction on target_user_id. The description only reinforces that sequence_id means a cadence filter implicitly; it adds no syntax or default behavior beyond the schema, so 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 and resource ('Conta matrículas agregadas por status e por step atual') and explicitly distinguishes itself from the list-fetching sibling by noting it works 'sem baixar a lista inteira'. An agent can immediately tell this is an aggregation/count tool rather than a paged list tool.

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?

Gives two concrete use cases: pre-flight sizing before a bulk action via manage_enrollment with sequence_id, and quick reporting on a cadence with thousands of enrollments. It names the downstream sibling tool, but does not explicitly say when to prefer list_enrollments or sequence_stats instead, so it stops short of full alternative routing.

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