media.project.create

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

With no annotations, the description must carry the full burden of behavioral disclosure, but it only states the action without noting side effects, idempotency, permissions, or what a manifest creation entails. The wording is minimal and does not reveal behavioral traits beyond the obvious write operation.

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 a single, tightly written sentence with no filler words. It is efficient, though perhaps too sparse to fully support tool invocation.

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 creation tool with no annotations, no output schema, and two unexplained required parameters, this description is insufficient. An agent cannot tell what a valid 'brief' looks like, what the response will be, or whether creating a manifest has side effects or prerequisites.

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 lists required fields 'name' and 'brief' but provides no property descriptions, and the description does not explain what these fields mean or how they should be formatted. The schema coverage signal is high only because the properties object is empty, so the description adds no meaningful parameter guidance.

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 uses a specific verb ('Create') and names the resource ('a media project manifest'), which clearly distinguishes it from read-oriented siblings like media.project.list and media.project.get. The term 'manifest' is somewhat specialized and could be clearer, but the primary purpose is unambiguous.

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 about when to use this tool versus alternatives such as media.storyboard.plan or media.compose. There is no mention of prerequisites, exclusions, or conditions that would route an agent to this tool over siblings.

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