check

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

No annotations are provided, so the description carries the full behavioral burden, and it leaves real questions open: whether calling it merely reads state or actively re-runs the test suites (potentially slow or costly), whether it is side-effect free, and whether any configuration is required. It does enumerate the return payload, which is its one behavioral contribution, but that is thin for an unannotated tool.

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 compact sentence that front-loads the core concept (engine health check) and then lists the payload items. No filler, no repetition of the tool name, and every clause carries information.

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 output schema, the description must explain the return values, and it does so by naming all five result categories, which is the critical piece for a zero-parameter diagnostic. What is missing is the operational framing — whether this is a cheap read or a heavier self-test — so it falls just short of 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already states. Baseline 4 applies; the description correctly avoids inventing parameter discussion.

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 frames the tool as an 'engine health check' (引擎体检) and enumerates exactly what comes back: version, passed tests, capability matrix, LLM availability, directory structure. That is a concrete, recognizable diagnostic purpose, and it clearly differs from the scraping-oriented siblings (scrape, crawl, screenshot). It stops short of explicitly naming when to prefer it over those siblings, but the intent is unambiguous.

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?

There is no guidance on when to call this tool: no mention of using it as a preflight/health-check step, no exclusions, no reference to alternatives among the sibling tools. An agent knows what it returns but not under what circumstances invoking it is appropriate or wasteful.

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