tokportal_get_video_analytics

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the behavior as a safe, idempotent read is clear. The description adds no additional behavioral context (e.g., response structure, data freshness, rate limits). With annotations covering safety, a score of 3 is appropriate.

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 short sentence, which is concise but lacks any structural detail. It earns its place but does not provide additional useful information beyond the tool name.

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?

Despite low complexity (one param, no output schema), the description omits what the tool returns (e.g., metrics, format). Without an output schema, the agent needs more context about the response. The description is too brief to be considered 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 provides 100% coverage with a single parameter 'id' described as 'Video ID.' The description does not add any further semantics beyond the schema. Given full schema coverage, the baseline is 3.

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 'Get single video analytics' clearly states the verb ('Get') and resource ('video analytics'), and the adjective 'single' differentiates it from list-oriented siblings like tokportal_list_account_video_analytics. However, the description does not elaborate on what specific analytics data is returned, leaving some ambiguity.

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 explicit guidance on when to use this tool versus siblings such as tokportal_get_analytics_series or tokportal_get_account_analytics. It does not mention use cases, prerequisites, or alternatives, relying solely on the tool name for differentiation.

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