blackboard_list_group_sets

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, openWorld). The description adds one genuine behavioral fact beyond them: the listing 'no garantiza acceso a detalles o integrantes', warning that member/detail data may be unavailable. It says nothing about pagination, filtering, or when that limitation applies, so it adds some but not rich context.

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 with no filler; the resource identification is front-loaded and the caveat follows. Terse without being padded, though the brevity contributes to the missing differentiation.

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 single-parameter read-only listing tool with no output schema, the description covers what is listed and one limitation, which is roughly the minimum. It omits the course-ID format and any routing guidance against the two group-related siblings, which an agent needs given the crowded toolset.

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% and the description never mentions 'courseId'. The parameter name is self-explanatory, but the required pattern '^_\d+_\d+$' (an unusual course-ID format) is documented nowhere, so the description does not compensate for the coverage gap.

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 identifies the resource ('Conjuntos de grupos publicados en un curso') and implies a listing operation, and the phrase 'mediante groups/sets' hints at the underlying endpoint. However, it never states the verb explicitly nor distinguishes this from the sibling 'blackboard_list_groups' (individual groups) or 'blackboard_get_group', so an agent must guess which listing tool to pick.

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 statement of when to use this tool versus 'blackboard_list_groups' or 'blackboard_get_group', and no prerequisites. The only guidance-like sentence is a caveat about the returned data, which is behavioral rather than usage-oriented.

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