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

Annotations already disclose readOnlyHint=true and idempotentHint=true, but the description adds no behavioral context beyond the endpoint string. It does not mention pagination behavior, scoping, auth implications, or how results are ordered.

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 extremely short and front-loaded, so there is no redundancy. However, it is under-specified rather than usefully concise, providing only an endpoint string with no explanatory substance.

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 list endpoint with nested query parameters and several sibling tools, the description omits what the tool returns, how to filter, and when to choose it. The output schema helps, but the description does not orient an agent enough to call the tool correctly.

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?

The description adds no meaning to either parameter. The schema documents workspaceId, but the nested query object's properties (limit, status, contentType, cursors) are left without explanatory context in the description.

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 is just 'GET /v1/media', which restates the tool name and endpoint without stating what the tool does in natural language. It implies listing media but does not explicitly differentiate from get_media_id or clarify the resource scope.

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 use this tool versus alternatives like get_media_id, post_media, or delete_media_id. An agent is left to infer the intended use case from the schema and sibling names alone.

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