vunet_query_metric

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

No annotations provided, so description carries full burden. It mentions automatic tenant configuration but does not disclose other important behaviors like effect of conflicting time parameters, error handling, response format, or pagination. Extensive schema descriptions exist but behavioral traits beyond parameter definitions are missing.

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?

Single sentence is concise and front-loaded with key information. However, given the tool's complexity (12 parameters), the description could benefit from additional structure (e.g., separate paragraphs for key features) while remaining concise. No redundancy.

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 tool with 12 parameters, no output schema, and no annotations, the description is too brief. It does not explain return values, time parameter combinations, error states, or the nature of the metric data returned. Schema covers parameters but not behavioral context needed for effective use.

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 coverage is 100% with detailed descriptions for all 12 parameters. The description adds minimal value by summarizing 'flexible time ranges and filters' but does not explain parameter relationships, defaults, or usage patterns beyond what schema provides. Baseline 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?

Description clearly states it queries a Vunet data model/metric, using verb 'Query' and specifying the resource. It distinguishes from siblings (vunet_fetch_datamodels, vunet_get_status, vunet_list_data_models) which are about managing models, not querying metrics.

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 on when to use this tool vs siblings or other alternatives. Does not mention prerequisites, contexts, or when to avoid using it. The only hint is 'automatically uses the configured tenant,' which is not a usage guideline.

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