health

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

Without annotations, the description carries the full burden. It states what is verified (API key and search capability) but does not mention whether the operation is read-only, what the response format is, or how failures are reported. This is a significant gap for a tool that may reveal system status.

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, concise sentence that front-loads the primary purpose. No unnecessary words or repetition, making it highly scannable.

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 health check with no parameters and no output schema, the description should explain what the user gets back (e.g., a status report or boolean). This is missing, though the tool's simplicity somewhat mitigates the impact. The absence of annotations also reduces completeness.

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 tool has zero parameters, and the schema coverage is 100%, so the baseline is 4. The description adds no parameter-specific details, which is acceptable since none exist.

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 explicitly states that this tool performs a health check to verify the DeepSeek API key and web search capability. This is a specific verb+resource combination, and it clearly distinguishes itself from sibling web_search tools by focusing on verification rather than performing searches.

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 implies usage for pre-checking API connectivity and search availability, but there is no explicit guidance on when to use it versus the sibling search tools. A clear statement like 'use this before other tools to ensure credentials are valid' would improve this.

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