VeoMCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns a 'Complete guide with prompt structure, examples, and tips,' which gives some output context, but lacks details on performance traits (e.g., response time, data freshness), error handling, or any constraints. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded, starting with the core purpose. The sentences are efficient and add value: the first states what it does, the second explains benefits, and the third specifies the return. There's minimal waste, though the second sentence could be slightly more concise by integrating benefits into the first.

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?

Given the tool's low complexity (0 parameters, no annotations) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose, benefits, and output format. However, it lacks behavioral context (e.g., whether it's cached or real-time), which would enhance completeness for a guidance 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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't mention any parameters, which is appropriate. It adds value by describing the output ('Returns: Complete guide...'), compensating for the lack of parameter details and aligning with the high schema coverage baseline.

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 clearly states the tool's purpose: 'Get guidance on writing effective prompts for Veo video generation.' It specifies the verb ('Get guidance') and resource ('prompts for Veo video generation'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'veo_text_to_video' or 'veo_image_to_video', which are for actual video generation rather than guidance retrieval.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions that following the tips helps with video generation, but doesn't specify scenarios (e.g., before using 'veo_text_to_video' for prompt crafting, or as a reference during troubleshooting). There are no exclusions, prerequisites, or comparisons to sibling tools listed, leaving usage context implied at best.

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