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

readOnlyHint=true is already declared, and the description reinforces it with 'a read-only search' plus the POST /v1/issuer/groups/search endpoint, so there is no contradiction. It adds genuine behavioral detail the annotations lack: AND-combination of filters, partial-match semantics, and the pagination contract for continuing a result set.

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?

Four tightly packed sentences, front-loaded with the resource definition before the filter, return, and paging details. Nothing is redundant, though the sentence mixing return fields with the endpoint is slightly overloaded.

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 10 optional parameters, no output schema, and a nested meta_data object, the description compensates well by listing the returned fields (id, name, course name and description, design ids, language, dates) and explaining pagination and filter combination. Coverage is close to complete for an agent to invoke it correctly.

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 the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: filters are ANDed together and name/course_name are partial matches. It also echoes the pagination contract. It does not clarify the date format or meta_data matching beyond what the schema already states.

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 ('Search groups') and goes further by defining what a group is ('an achievement such as a course or qualification that credentials belong to'), which an agent needs since 'group' is ambiguous. Combined with the 'Search' verb versus the sibling accredible_get_group, the agent can distinguish this tool from its nearest neighbor without opening the 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?

Gives real usage context: filters combine with AND, name and course_name match partially, and paging works by passing meta.next_page as page. It does not, however, name when to prefer this over siblings such as accredible_get_group or accredible_search_collections, so the routing guidance is implied rather than explicit.

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