clickup_get_operation

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 behavioral beyond that — it does not say where a valid operation_id comes from or what happens with an unknown ID — so it sits at the annotated baseline.

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?

A single front-loaded sentence that lists the inspected artifacts with zero filler. Every clause earns its place for a tool of this simplicity.

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?

An output schema exists, so explaining return shape is unnecessary, and the description covers it lightly. The missing pieces are the workflow prerequisite for obtaining operation_id and any pointer to the search sibling, which an agent needs to call this tool successfully.

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 is one required parameter (operation_id) with 0% schema description coverage, so the schema carries no meaning. The description does not explain that operation_id must be harvested from clickup_search_operations or give any format/example, leaving the sole input effectively undocumented.

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 ('Inspect') and resource ('operation') and enumerates what is inspected (description, path/query parameters, body schema), so the agent knows exactly what comes back. It does not, however, name or contrast itself with the sibling clickup_search_operations, so the get-vs-search distinction must be inferred.

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 when-to-use statement, no prerequisite (e.g. that operation_id comes from clickup_search_operations), and no exclusion against siblings. The intended usage is only weakly implied by the phrase 'an operation's'.

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