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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds nothing beyond that—no note on scoping, response shape, or whether labels are workspace- or module-specific—and only redirects to describe_operation.

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?

It is short, but the opening sentence is duplicated verbatim, and the remaining content is an operation ID plus a pointer elsewhere. Brevity here reflects under-specification rather than efficiency.

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 tool with a nested/free-form query parameter, no output schema, and no parameter documentation, the description should say what the endpoint returns and how to scope the request. It supplies neither, so an agent cannot decide whether this is the right settings endpoint or how to call it without a second tool.

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 two parameters: a free-form 'query' object and an empty 'params' object, both entirely undocumented. The description does not describe either; the redirect to describe_operation is a partial mitigation but leaves the caller with no in-definition semantics.

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 repeats the endpoint path 'GET /api/settings/field-labels' twice, which is essentially a restatement of the tool name and title. It never explains what a 'field label' is or what the response contains, and it offers no differentiation from neighbors such as get_settings_module_labels or get_settings_site_contact_types.

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 guidance on when to call this versus the many other settings GET tools. The only actionable direction is a pointer to describe_operation for native request schemas, which is a schema-lookup hint rather than a usage condition.

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