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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds pagination behavior (100 per page) and clarifies that returned dates are YYYYMMDD while the filter params use yyyy-mm-dd — useful, but it says nothing about the count_only mode, ordering of results, or permissions scope.

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?

Three short sentences: what is returned, how to filter, and pagination mechanics — front-loaded with the resource and field list, with no filler. Slightly dense but every clause carries information.

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?

With 12 parameters, no output schema, and read-only annotations, the description does the important work of enumerating the returned fields and the page size, compensating for the missing output schema. The undocumented count_only shortcut and result ordering are the remaining gaps.

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 92%, so the schema already documents the filter grammar, operators, and date patterns in detail. The description only groups the filters into users/number/method/dates, adding little beyond that baseline; the output-vs-filter date format hint is the one real contribution.

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 resource and scope: certifications issued within one certification program, with the returned fields enumerated. It does not name or differentiate itself from plausible siblings such as axislms_list_user_certificates, axislms_list_certification_users, or axislms_get_certification, so an agent must infer the distinction.

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?

"Filter by users, number, method and dates. Paged (100 per page)" implies how to narrow results, but there is no explicit when-to-use guidance, no exclusions, and no pointer to the sibling that returns a single certificate or a per-user certificate list.

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