get_video_rule_profileRetrieves a video rule profile's requirements, recommendations, and source URL by its ID to provide detailed configuration details.
Return one Video profile with separate requirements, recommendations and source URL.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Video rule profile id from list_video_rule_profiles. |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden and does state the returned content: requirements, recommendations, and source URL. However, it does not mention error behavior, behavior for unknown ids, or whether the source URL indicates remote fetching.
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, efficient sentence with no filler. It front-loads the core action and packs the distinguishing output details into a compact structure.
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 one-parameter get operation, the description is nearly complete: it explains what is returned and the schema supplies the required id. It is missing minor details like not-found or error behavior, but nothing essential for selecting and invoking the 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?
Schema description coverage is 100%, and the id parameter is already documented with provenance ('from list_video_rule_profiles'). The tool description adds little parameter meaning beyond the schema, so the baseline of 3 is appropriate.
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 action ('Return one Video profile') and details the result contents: separate requirements, recommendations, and source URL. The singular 'one' clearly differentiates this from list_video_rule_profiles, and the 'Video' qualifier separates it from the generic get_rule_profile sibling.
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 gives no guidance on when to use this tool versus alternatives such as list_video_rule_profiles or get_rule_profile. The only routing hint appears in the schema's parameter description ('id from list_video_rule_profiles'), not in the tool description itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.