list_groups

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

With no annotations provided, the description carries the full burden. The verb 'List' implies a read-only operation, and the description discloses the return fields, which is useful. However, it does not mention potential volume, pagination, authentication requirements, or any side effects. It is adequate but lacks rich behavioral context beyond the obvious read-only nature.

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?

The description is a single, well-structured sentence that front-loads the core purpose ('List all note groups') and then specifies the output fields. There is no unnecessary verbosity or repetition; every word earns its place.

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?

Given the tool has no parameters, no output schema, and no annotations, the description must convey the return values. It specifies the exact fields (group name, UUID, note count), which is sufficient for an agent to understand the result. The only minor gap is the lack of explicit mention of the return structure (e.g., an array of objects), but this is reasonably inferred from the context.

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?

The tool has zero parameters, and schema description coverage is 100%, so there is no parameter information missing. The description adds no parameter semantics, but with 0 parameters this is not needed. The baseline for 0 parameters is 4, and the description does not need to compensate for any gaps.

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 clearly states a specific verb ('List'), a specific resource ('note groups in the project library'), and scope ('all'). It also lists the returned fields (group name, UUID, note count), making the tool's purpose distinct from siblings like list_tracks or get_notes.

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?

The description implies when to use the tool by specifying the resource (note groups), but it provides no explicit guidance on when to prefer this over siblings or any exclusions. The presence of sibling tools like list_tracks and get_notes means an agent could infer usage, but the description itself carries no direct usage instructions.

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