Media Type Create

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

With no annotations, the description carries full responsibility for behavioral disclosure. It implies a create/mutation operation but says nothing about required permissions, whether id must be unique, what source_configuration does, or whether the operation can fail if the media type already exists.

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 single sentence is front-loaded and not bloated, but it is drastically under-specified for a five-parameter configuration entity creation tool. Conciseness here comes at the cost of necessary structure and information.

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?

Although an output schema exists, the description must still cover the call semantics, and it does not. With no annotations, 0% schema description coverage, and five parameters for a config entity creation tool, the one-sentence description is completely inadequate.

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 schema has five parameters with zero description coverage, including non-obvious ones like source and source_configuration. The description provides no meaning for any parameter, so it fails to compensate for the schema 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 'Create a new media type' simply restates the tool name and title, making it tautological. It states a verb and resource but provides no differentiation from sibling tools such as media_type_list, media_type_get, or create_media.

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 guidance, prerequisites, or alternatives are provided. The agent is not told when to choose this tool over media_type_get, media_type_list, or create_media, leaving selection entirely to inference from the name.

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