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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing that the default response is a truncated 'short summary' and that `fields` is needed for full records, but it omits pagination/limit behavior despite exposing a limit parameter.

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 clauses, front-loaded with the purpose and the concept definition before the practical hint. No filler, though the raw endpoint path is of marginal value to an agent versus the rest of the sentence.

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 read-only, zero-required-parameter list tool with no output schema and full schema coverage, this covers what the agent needs: what the resource is, and that the default result is abbreviated unless `fields` is supplied.

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%, documenting both `limit` (1-1000, default 100) and `fields` with the pattern and example. The description's `fields` example duplicates the schema; it adds the rationale (summary vs full) but nothing about `limit`.

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 (list label groups) and adds a clarifying gloss that distinguishes them from labels themselves, which implicitly separates it from the sibling list_labels. It does not explicitly name that sibling, so it stops short of full differentiation.

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?

It gives one actionable usage cue — pass `fields` when the short summary is insufficient — but says nothing about when to choose this tool over scheduleit_list_labels or scheduleit_get_group, and offers no prerequisites.

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