medias_create_media_folder

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral detail. It doesn't explain side effects, required permissions, or what happens to the created folder. The description provides zero additional transparency beyond the annotations.

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?

Two words is not conciseness; it's under-specification. There is no structure or front-loading of important information. The description fails to provide any useful detail and thus does not earn its place.

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 tool with 4 parameters and no output schema, the description is drastically incomplete. It doesn't explain the purpose of the media folder, where it is created, any constraints, or what the return value might be. An agent cannot correctly infer when and how to call this tool.

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 input schema has 100% description coverage for all 4 parameters, so each is well-documented. The description adds no parameter-level context, but the schema already handles it. A baseline of 3 is appropriate since the schema covers the parameter semantics fully.

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 Folder' essentially restates the tool name without adding specificity. It doesn't distinguish this tool from other folder-creation tools like custom_fields_create_custom_field_folder or clarify that this is a media-focused folder. The verb and resource are present, but the description is a tautology that provides no differentiation.

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. No mention of prerequisites, context, or exclusions. The description offers no information to help an agent decide when to invoke this tool instead of any other create tool.

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