Media Type Get

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read, but it says nothing about permissions, behavior when the ID does not exist (error vs empty), or the meaning of the include parameter. An output schema exists, so return format need not be described, but the operation's failure semantics remain undisclosed.

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 with zero waste, but it is undersized rather than genuinely concise given two undocumented parameters and no annotations. Efficiency is fine; coverage is thin.

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 simple fetch tool the description is near the minimum viable, but with no annotations, 0% schema coverage, and an undocumented 'include' parameter, key details are missing. The output schema excuses explaining return values, yet usage and parameter context are still absent.

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%, so the description must compensate. 'By ID' loosely maps to media_type_id, but the 'include' parameter is entirely undocumented in both schema and description, leaving half the parameters with no semantics.

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?

Clear specific verb+resource ('Get a single media type by ID'), so the agent knows exactly what it retrieves. However, it does not distinguish itself from the sibling media_type_list, which an agent could confuse it with for retrieval tasks.

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 on when to use this versus media_type_list or media_type_create, and no prerequisites or conditions stated. The agent must infer that 'single by ID' means use this instead of the list variant.

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