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

With no annotations, the description carries the full burden, but it reveals nothing about behavior—no mention of read-only nature, pagination, rate limits, or data scope. It only states billing costs, which is not behavioral context.

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 but not useful; it is under-specified. It includes billing information that does not help with tool usage, wasting space. The layout is not the concern; the content is inadequate.

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 an endpoint with three parameters and no output schema, the description fails to explain what the tool returns, how pagination works, or even why the 'id' parameter is needed. The billing mention is irrelevant. The description is far from enough for an agent to use it 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?

Schema description coverage is 100%, so the parameters are already documented in the schema. The description does not add any extra meaning beyond the schema; baseline 3 is appropriate since schema covers all parameters. No contradiction or missing 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 only repeats the title 'User Media' without stating what the tool actually does. It lacks a verb and resource, making it impossible to determine whether it fetches media items, lists media, or something else. It does not differentiate from siblings like get_v2_UserTweets or get_v2_UserHighlights.

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 guidance is provided on when to use this tool. It does not mention any context, prerequisites, or alternatives. The only content is billing information, which is irrelevant to usage decisions.

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