get_ksqldb_info

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description adds no extra behavioral context. It does not explain what 'server info' includes, whether authentication is needed, or what the response looks like, leaving the agent reliant entirely on the annotations.

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, front-loaded sentence with no filler or redundancy. It is appropriately concise for a simple getter, though it could have been slightly more informative without becoming bloated.

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?

Since there is no output schema, the description should compensate by explaining what 'server info' returns, but it does not. Given the large sibling set and vague scope, an agent would be uncertain about the tool's exact output and when it is the right choice.

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 100%, with both parameters (ksqldb and cluster) documented in the schema. The tool description adds no additional meaning about the relationship between the parameters or how they should be supplied.

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 a clear verb ('Get') and resource ('ksqlDB server info'), which helps distinguish it from sibling tools focused on specific ksqlDB objects like queries, streams, and tables. However, 'server info' is somewhat vague and does not specify exactly what information is returned.

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 about when to use this tool versus the many ksqlDB-related siblings such as get_ksqldb_queries, get_ksqldb_streams, or get_ksqldb_tables. There are no explicit context cues, exclusions, or alternative routing.

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