clickup_get_operators

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

With no annotations, the description carries the full burden and does disclose important behavior: the output is Markdown, it includes HTTP routes, parameters, and request/response body schemas, only enabled operators are shown, and the catalog grows over time. It does not explicitly state that the tool is read-only or mention auth/rate-limit implications, which keeps it short of a 5 for a no-annotation tool.

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 description is front-loaded with the core behavior and then layered with routing guidance. Every sentence earns its place: it explains what is returned, when to call it, why it exists, and how it relates to `clickup_execute_operator` without padding.

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?

Given the tool has no output schema and no annotations, the description still explains the return format and content in enough detail for an agent to use it correctly. It covers scope, filtering context, catalog growth, and the relationship to the execution tool, leaving no critical ambiguity for this read-only metadata operation.

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 100%, so all three filtering parameters (`models`, `workspace_id`, `model_operators`) are already documented in the schema. The description does not add filtering syntax or use-case guidance beyond that baseline, which is appropriate but not value-adding.

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 a specific verb and resource: it lists enabled Unified API operators as `<model>.<operator>` pairs along with routes, parameters, and schemas. It immediately distinguishes this catalog from the dedicated `clickup_*` tools and names `clickup_execute_operator` as the companion tool, so an agent can identify its role without opening the schema.

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?

It explicitly says when to call it: whenever no dedicated tool fits, when a request spans many objects, and always before `clickup_execute_operator`. It also establishes the negative case by framing dedicated tools as the default alternative, and tells the agent to use this catalog instead of inferring capability from names or descriptions.

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