check_compatibility

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core function but reveals no behavioral traits — no read-only guarantee, no side-effect information, no indication of what the verdict looks like, and no mention of whether all factors must be supplied. It is not misleading, but it is thin for a tool with zero annotation coverage.

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 front-loaded sentence states the purpose and enumerates the factors with zero filler. While it is thin relative to the tool's complexity, as pure conciseness the structure is efficient and every word earns its place.

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 an 8-parameter tool with no annotations and 0% schema coverage, one sentence under-specifies. The output schema covers return values, but the required skill_id is unexplained, usage context is absent, and the agent gets no sense of which parameters to provide in which scenario.

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%, so the description must compensate. It does enumerate the dimension parameters (operating_system, mcp_client, installed_software, has_gpu/has_hpc, available_licenses, api_access), which adds some conceptual meaning, but it never mentions the required skill_id and gives no format or value semantics for the array 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 uses a specific verb (判断/determine) and identifies the resource (compatibility) along with the factors considered: OS, MCP client, software, GPU/HPC, licenses, and API. It is inherently distinct from the sibling tools, which are all search/get/diff/report operations, though it never explicitly names the skill being checked — the required skill_id parameter must carry that implication.

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?

No guidance is provided on when to use this tool versus alternatives such as search_skills, doctor, or get_skill_card. The only usage signal is the implied scenario of checking a skill against an environment, which an agent must infer from the single purpose sentence rather than from explicit direction.

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