checkPlatformDependencies

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'check' implies a read-only diagnostic operation, the description doesn't clarify what 'installation status' means (e.g., returns boolean, list of missing dependencies, detailed report), whether it has side effects, or what permissions/context it requires. This leaves significant behavioral uncertainty.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple diagnostic tool and front-loads the core functionality.

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 simple diagnostic tool with one well-documented parameter and no output schema, the description is minimally adequate. However, it lacks important context about what the check returns (status format, error conditions) and how it relates to the sibling 'installPlatformDependencies' tool, which reduces completeness for practical agent usage.

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 100%, with the single parameter 'platform' clearly documented in the schema as a required enum with values 'android' or 'ios'. The description adds no additional parameter semantics beyond what the schema already provides, which meets the baseline expectation when schema coverage is high.

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 verb ('check') and resource ('installation status of platform dependencies and tools'), making the purpose understandable. However, it doesn't explicitly differentiate from the sibling tool 'installPlatformDependencies', which could create ambiguity about when to use each tool.

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. With a sibling tool named 'installPlatformDependencies', there's a clear related alternative, but the description doesn't mention it or provide any context about prerequisites, timing, or workflow sequencing.

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