Get VWO metric report

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

The description states 'get the details', which aligns with the readOnlyHint annotation indicating a safe read operation. No additional behavioral context is provided beyond what the annotations already convey.

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 concise sentence with no unnecessary words, enabling quick comprehension.

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 lack of an output schema, the description does not specify what details are returned (e.g., metrics, time range). The description is adequate but could be more informative about the response structure.

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%, with each parameter having a clear description. The tool description adds no further semantic nuance beyond what is already in the schema, so a baseline score applies.

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 verb 'get' and the resource 'details of one VWO Insights metric report by its id', distinguishing it from the sibling tool vwo_list_metric_reports which lists all metric reports.

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 itself does not provide explicit guidance on when to use this tool vs alternatives. However, the input schema description for reportId instructs to call vwo_list_metric_reports if the id is unknown, providing indirect usage guidance.

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