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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond an opaque operation ID; it doesn't say what the endpoint returns, whether the field list is workspace-scoped, or how large the payload is.

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 path is repeated twice identically, wasting the entire first half of the description, and the operation ID plus schema pointer follow with no front-loaded purpose. It is short but for the wrong reason — under-specification, not 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 annotation-level clues about the data shape, the description supplies none of the missing context. An agent would have to call describe_operation and then still not know when this endpoint is the right choice.

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?

There are two parameters (a free-form 'query' object and an empty 'params' object) with 0% schema description coverage and nested objects. The description provides no information about what belongs in 'query', which keys are accepted, or what 'params' does, so an agent has to guess.

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 states only the raw endpoint path 'GET /api/approvals/condition-fields', duplicated verbatim, which merely restates the title. It never says in plain language what a 'condition field' is or what the response represents, so an agent cannot distinguish this from siblings like get_approvals_workflows or get_automation_workflows_condition_fields beyond the URL string.

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 only routing hint is 'describe_operation provides native request schemas', which points to a helper tool but gives no when/when-not guidance or comparison to the many sibling approvals endpoints. There is no statement of context in which an agent should call this versus get_approvals or get_approvals_workflows.

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