get_current_metrics

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

With no annotations, the description carries the full transparency burden. It does disclose one behavioral trait beyond the schema: fetching all queues when queue_ids is omitted. However, it omits other behavioral details such as required permissions, rate limits, or result structure (though the output schema covers return values).

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 extremely concise: two sentences, front-loaded with the core purpose, and no wasted words. Every sentence adds meaningful information.

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?

An output schema exists, so return values are documented. However, the description is sparse on context: it doesn't explain the required instance_id, the valid values for channel, or how this tool relates to similar analytics tools. The conditional queue_ids behavior is a positive, but overall the description leaves important gaps for an agent to fully use the tool correctly.

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 0%, so the description must compensate for the lack of parameter documentation. It only explains queue_ids behavior ('If no queue_ids provided, fetches all queues first'), but leaves channel and instance_id completely unexplained. This is insufficient for an agent to understand all parameter meanings.

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 function: 'Get real-time metrics for queues and agents.' This is a specific verb+resource, but it does not explicitly distinguish itself from sibling tools like analytics_get_metric_data or analytics_get_current_user_data, though the real-time queues/agents focus provides some differentiation.

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 offers no guidance on when to choose this tool over alternatives. The only usage hint is the conditional behavior with queue_ids ('If no queue_ids provided, fetches all queues first'), which is more about input handling than usage context. No alternatives or exclusion criteria are mentioned.

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