Create check

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

With no annotations, the description carries full burden. It only says 'Create a new check' and gives no information about side effects, permissions, idempotency, what constitutes a valid check, or behavior on duplicate names or missing required fields.

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 sentence, very concise and front-loaded. However, it is under-specified to the point of being unhelpful, as it omits any detail that would justify its brevity.

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?

This is a creation tool with 9 optional parameters, no annotations, and no output schema, yet the description offers no context about what a check is, how checks are configured, or what fields are relevant in different scenarios. The description is far from complete for a tool of this complexity.

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 description provides no parameter information. Even though schema description coverage is 78%, the description does not clarify how parameters like schedule versus timeout relate to check types, which fields are required for simple vs. cron checks, or how the 'unique' array works.

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 states the action 'Create' and the resource 'check', which is clear and specific. However, it does not distinguish from sibling tools like update_check or pause_check, lacking scope or type of check being created.

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 update_check or schedule vs. simple checks. The description does not indicate any prerequisites, preferred usage patterns, or exclusions.

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