media.project.list

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

No annotations are provided, and the description only says 'List media projects,' which implies a read-only operation but adds no detail about pagination, ordering, result shape, permissions, or side effects. The description is not misleading but is behaviorally minimal.

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 terse sentence with no wasted words. It is appropriately sized for such a simple zero-parameter listing operation.

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 zero-parameter list tool, the description is minimally adequate, but with no output schema and no annotations, it provides no return-format context or broader discovery guidance. An agent can call it, but not know what shape the results take or how this listing relates to get/create.

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 tool has zero parameters and the schema coverage is trivially 100%, so the description has nothing meaningful to add. The additionalProperties: true flag is slightly ambiguous, but with no defined parameters, this is not a significant 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 states a specific verb, 'list', and a specific resource, 'media projects'. The plural 'projects' clearly differentiates it from sibling tools like media.project.get and media.project.create.

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 about when to use this tool versus alternatives. No conditions, exclusions, or sibling comparisons are provided, so an agent must infer when listing projects is appropriate.

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