server_status

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

No annotations are provided, so the description must carry the full burden. It does not state whether the operation is read-only, requires special permissions, or has side effects. The 'Runs in your Kuudo deployment' note is environmental, not behavioral.

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 short, but the opening 'Catalog entry.' is cryptic and may confuse agents into thinking it is a placeholder rather than a functional tool. The second sentence is clear and front-loaded, but the first sentence wastes space.

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?

It lists the diagnostic areas, giving an idea of the scope, but does not describe the output format, error handling, or any prerequisites. Without an output schema, the description should provide more detail on the return value to be fully complete.

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?

There are zero parameters, so the description has nothing to add. Baseline of 4 is appropriate since no parameter documentation is needed.

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 server diagnostics and enumerates the specific areas (auth, models, storage, uploads, resources, health). This is a specific verb-resource pair and distinguishes it from all sibling tools, none of which mention diagnostics.

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 purpose is obvious from the name and description, and the note 'Runs in your Kuudo deployment, not here' gives contextual placement. However, it does not explicitly state when to use this over alternatives, though no sibling offers diagnostics, so it's effectively the only choice.

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