dashai_server_info

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds the exact return JSON schema and failure response format, giving deeper insight into behavior beyond 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 well-structured and front-loaded with the purpose, followed by usage timing and a clear return schema. Every sentence earns its place, and the failure format is stated compactly.

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 simple diagnostic tool with no arguments, the description fully covers purpose, when to use, return values, and error handling. The embedded output schema means no return value ambiguity remains, making it complete for this 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?

The schema includes a single NoArgs parameter with no properties, but the description explicitly states 'params (NoArgs): no parameters,' confirming the tool takes no meaningful arguments. This adds clarity beyond the raw schema and fully compensates for the 0% coverage since there are no real parameters.

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 'Checks that dashAI is running and summarizes what is loaded,' using a specific verb and resource. It distinguishes itself from sibling tools by positioning it as the first call for diagnostics, which is unique among the listed tools.

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?

Explicitly instructs to 'Call this FIRST when something fails or when you do not know whether the backend is up,' and explains how it disambiguates two failure types. This provides strong when-to-use guidance and implicitly contrasts with other tools.

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