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, and merely notes that describe_operation exposes native request schemas; it does not say whether results are paginated, scoped to a workspace, or filtered by contract/COI.

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 text is short but wastes its opening on a verbatim duplicate of the endpoint path, and the only substantive content is an operation ID plus a pointer to another tool. Brevity here reflects under-specification, not efficient expression.

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?

There is no output schema, zero schema description coverage, and no annotation-independent explanation of results. For a two-parameter read endpoint in a large sibling toolset, the description leaves an agent unable to know what it will get back or what the query/params objects should contain without first invoking describe_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 0% for two nested parameters (query, params) that are otherwise opaque object bags with additionalProperties. The description offers no parameter meaning at all, only a redirection to describe_operation, which does not compensate for the coverage gap.

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 only repeats the raw endpoint path 'GET /api/coi-upload-tokens' twice, which is a tautological restatement of the tool name/title. It conveys that this is a read of a 'coi-upload-tokens' collection but never says what an upload token is, what the response contains, or how it differs from siblings like get_coi_list.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative sibling is named other than the generic pointer to describe_operation. An agent knows only that it may call describe_operation for schemas, which is workflow plumbing rather than usage guidance for this tool.

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