start_ext_check_collection

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

Annotations already indicate this is a non-destructive, non-idempotent, open-world mutation. The description adds nothing beyond that: it does not explain what starting a collection does, whether it is asynchronous, what side effects occur, or what the result represents.

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 short and front-loaded, but it redundantly repeats the same idea: 'Start check collection' followed by 'Start a new check collection.' The endpoint annotation is the only additional information, and the second sentence does not add much.

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 mutation tool with a nested request body and no output schema, the description is too thin. It does not explain what a check collection is, what starting one entails, whether the operation is asynchronous, or what an agent should expect after invocation.

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%, including descriptions for objectId, objectType, checkCollectionTemplateId, and x-trace-id, so the schema carries parameter semantics. The description adds no additional meaning about the required body or how the vserver/template IDs are used.

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 a specific verb and resource: starting a check collection, and the endpoint hints at the API operation. However, 'check collection' is undefined, and the description does not distinguish this tool from closely related siblings such as start_ext_check or list_ext_check_collections. The second sentence largely repeats the title.

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?

There is no guidance on when to use this tool versus alternatives such as start_ext_check or the collection retrieval/cancel tools. No prerequisites, such as needing a template ID or a vserver object, are mentioned.

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