get_topic_partition_metrics

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

No annotations provided, so description must cover behavioral traits. Only states 'Get metrics' without confirming read-only nature, what metrics are returned, or any rate limits/pagination. Output schema exists for return values, but behavior beyond that is undisclosed.

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?

Description is a single 6-word sentence, extremely concise with no superfluous words. It front-loads the essential purpose and does not waste words, though it could benefit from slight expansion.

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 five parameters (two required) and no annotations, the description is too minimal. It lacks context on how to use the optional time parameters, what metrics are returned, and any prerequisites. Output schema helps but does not compensate for missing usage context.

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% (no parameter descriptions in schema). The description adds no meaning to the five parameters beyond what is inferred from their names and types. For example, 'duration' and time range parameters are unexplained, making it unclear how they affect the query.

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 the tool gets metrics for a specific topic partition using the verb 'Get' and resource 'metrics for a specific topic partition'. This distinguishes it from sibling tools like get_topic_metrics (entire topic) and get_topic_partition_infos (partition info).

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 versus alternatives. Does not specify that it is for a specific partition, nor contrasts with other get_* tools. An agent would need to infer from the name alone.

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