media.project.get

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

Without annotations, the description carries the burden of behavioral disclosure. 'Read' clearly implies a non-mutating retrieval operation, which is important context. However, it does not describe what is returned, how failures are handled, or any access considerations, so transparency is only 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 focused sentence with no filler or redundant phrasing. It is concise and front-loaded, though it sacrifices useful detail by being so terse.

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 read operation, the core purpose is present and an agent can probably invoke it with projectId. But there is no output schema and no mention of the return value, projectId semantics, error behavior, or when to prefer list/get, leaving the definition minimally viable rather than complete.

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 requires projectId but defines no properties, and the description never mentions projectId or how to identify which media project to read. Even though schema description coverage is reported high, that is only because the properties object is empty; the one meaningful required parameter is effectively undocumented.

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 clear verb ('Read') and resource ('a media project'), so an agent can understand the basic operation. It could be more specific by mentioning retrieval by projectId, but 'a' plus 'read' loosely distinguishes it from media.project.create and media.project.list.

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 given about when to use this tool versus siblings like media.project.list or media.project.create. There is no statement of what kind of project lookup this is for, nor any exclusion or alternative routing. The agent must infer usage from the tool name and sibling set.

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