ascend_env_check

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

With no annotations, the description must disclose behavior; it does state 'read-only', which is a key safety trait. However, it doesn't describe what the output contains beyond the hints, or any prerequisites/errors. The output schema covers return format, but behavioral context like side-effect freedom is minimal.

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, front-loaded with the key phrase 'Read-only', and every word adds meaning. It doesn't waste 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?

Given the tool has no parameters and an output schema exists, the description provides the essential purpose and read-only guarantee. It could mention when to run it, but the scope is fairly obvious from the name and sibling 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 tool has no parameters, so the description doesn't need to explain parameter details. It adds context by listing the areas the check covers, which gives meaning beyond an empty schema.

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 uses 'read-only Ascend/CANN environment check' which clearly identifies the operation as a query and specifies the resource. It lists concrete items checked (devices, HCCL preload, Docker hints), differentiating it from sibling health/status 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?

The description implies this is a read-only environment inspection tool but does not explicitly state when to choose it over sibling tools like repository_health or collective_status. There's no stated alternative or exclusion, so usage context is implicit.

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