partition_state

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It doesn't disclose whether this is a read-only operation, whether it returns raw metrics or computed diagnostics, or what 'leader skew' implies for interpretation. The read-only nature is implied but never stated, and no context is given about what the returned data means or how it should be used.

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?

A single sentence that conveys the tool's function efficiently. Zero wasted words; the description is appropriately sized for a straightforward read tool.

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?

With no annotations, no param descriptions, and no usage guidance for a diagnostic tool among seven siblings that could all plausibly be invoked for similar questions, the description is too thin. The output schema exists but the description doesn't explain what consumers should do with the returned leader skew or ISR state, leaving the tool's interpretive value unexplained.

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?

Despite 0% schema description coverage, the description contextually connects the single 'topic' parameter to the leader/ISR state reporting. The single parameter is self-explanatory given the tool purpose, so the schema plus description is adequate. However, the description adds no format, range, or example values beyond what the schema title 'Topic' provides.

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 states the tool reports 'Leader/ISR state per partition' with leader skew across brokers, which is a specific resource and provides the core purpose. However, it doesn't offer terminology that would help an agent distinguish it from siblings like cluster_health or topic_audit, and it leaves the metric interpretations vague.

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 when-to-use guidance is provided. The description doesn't state when to choose this over cluster_health (health at cluster level), topic_audit, or consumer_lag. No exclusions or preferred contexts are mentioned, leaving the agent to infer based on the tool name alone.

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