mat_healthcheck

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

No annotations are provided, so the description must fully disclose behavior. It states the tool validates, but it does not explain side effects (likely none), required permissions, rate limits, or output format. With zero behavioral context, the AI agent cannot anticipate the tool's impact or constraints.

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 communicates the core purpose without extraneous words. While it is very brief, it earns its place by being direct. However, it could be slightly more informative without losing conciseness.

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 lack of output schema and annotations, the description should provide a more complete picture of what the tool returns (e.g., success/failure status, details of validation). It also omits any information about error handling or the scope of validation. The sibling tools suggest a suite of MAT-related operations, but this description does not integrate the health check into that 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?

Schema description coverage is 0%, meaning the input schema provides no parameter descriptions. The tool description mentions 'MAT launcher and Java runtime availability,' which hints at the purpose of 'mat_home' and 'java_path,' but does not explicitly define their meaning, expected format, or whether they are required. This leaves significant ambiguity.

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's purpose: 'Validate MAT launcher and Java runtime availability.' It uses a specific verb ('validate') and resource ('MAT launcher and Java runtime availability'), and it distinguishes the tool from its siblings (which focus on index status, OQL queries, specifications, and reports). This makes the tool's role in the ecosystem obvious.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or cases where another tool like 'mat_index_status' would be more appropriate. This leaves the AI agent without decision-making support for selecting this tool.

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