GET /statuslabels/{id}

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered structurally. The description adds nothing beyond that – it does not mention 404 handling for unknown ids, auth requirements, or what a status label record contains, making it a restatement of the title.

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 the operation front-loaded, easy to parse. The trailing 'Generated from Snipe-IT OpenAPI operation statuslabelsid' is provenance noise that consumes space without helping the caller.

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 plain GET with no output schema, the description should hint at the returned record's fields (name, type, color, defaults) and error behavior. It provides none of that, leaving an agent unable to anticipate the response payload.

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% for the single integer id parameter, so the description must compensate. The path template '{id}' plus 'View a status label' signals that id is a status label identifier, which is a marginal gain, but it never clarifies type scope, valid ranges, or what an id refers to.

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 ('View') and resource ('a status label') resolved by path id, so the agent can tell it from list-style siblings like snipeit_list_statuslabels. It does not, however, distinguish itself from the many near-duplicate gen_statuslabelsid variants (snipeit_gen_statuslabelsid_1/_2/_3) 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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusion of the sibling endpoint that returns a status label's assets. The only cue is the implied 'single record by id' shape of the path.

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