get_broker_metrics

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

With no annotations, the description must disclose behavioral traits, but it only hints at two modes ('curated' and 'raw') without explaining what each entails. It does not state read-only status, defaults (e.g., when broker_id is null), pagination, or error handling. The description is too terse to convey necessary behavior.

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 that front-loads the core purpose without waste. Every word contributes to defining the tool's function, making it easy to scan.

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 having an output schema, the tool has five optional parameters and no annotations. The description fails to provide usage context, parameter semantics, or behavioral details. An agent cannot confidently invoke this tool correctly without additional schema inspection and heuristics, making it incomplete for this complexity level.

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 five parameters, but it does not. Only vague hints exist: 'one or all brokers' implies broker_id, and 'curated or raw' might relate to include_raw, but metric_name and label_filters are completely unexplained. The description adds minimal value over the bare schema.

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 returns JMX Exporter metrics, specifies 'curated or filtered raw' as the nature, and scopes to 'one or all brokers.' This distinguishes it from siblings like get_topic_metrics (topic-level) and describe_brokers (metadata), so the purpose is unambiguous.

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 is provided on when to use this tool versus alternatives. It does not mention conditions (e.g., 'use for broker-level metrics' or 'for topic metrics, use get_topic_metrics'). An agent would have to infer usage from the name and surrounding tools, which is insufficient.

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