List status labels

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description's only behavioral content is 'paginated list' and 'supports search', both of which are already documented in the input schema (the all/limit parameters spell out pagination and truncation semantics). It adds no context on result shape, sorting, rate limits, or the 10,000-row cap.

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 clauses, front-loaded with the verb and resource; no filler. It is close to under-specified rather than verbose, but nothing needs deleting.

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 zero-required-param read-only list tool with coverage from annotations and a mostly-described schema, this is minimally adequate. Gaps remain: no mention of the status_type filter, no hint of the response envelope, and no differentiation from the duplicate sibling tools.

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 coverage is 60%: offset and search are undocumented in the schema, and the description's phrase 'supports search' adds partial meaning for the search parameter. It says nothing about the status_type enum filter, which is documented in the schema but is the main way to narrow results.

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 the endpoint and resource explicitly ('GET /statuslabels') and characterizes the result as a paginated list supporting search. An agent can identify it as a read/list operation on status labels, though it does not differentiate itself from the near-duplicate siblings like snipeit_gen_statuslabels or from snipeit_get_statuslabel_assets.

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?

No guidance on when to choose this tool over the many alternative list/get status-label tools in the sibling set, and no preconditions or exclusions are stated. The agent must infer usage from the name alone.

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