Create child issues

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

The description adds the authorization class 'board_or_agent' which provides behavioral context beyond annotations. However, it does not disclose other important behaviors like side effects on the parent issue or subtree, or whether creation is synchronous. Annotations already indicate non-read-only and non-destructive, so the description adds mild value.

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 very concise, consisting of two short sentences. There is no fluff, and the technical details (operation, authorization class) are efficiently presented. However, it lacks structure that could improve scannability.

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 high complexity (many parameters, nested objects, output schema), the description is extremely incomplete. It does not explain the purpose of the parent ID, required fields in the body, or typical usage. Even with an output schema, the description fails to provide sufficient context for correct 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?

The description does not describe any parameters. With 0% schema description coverage, it provides no guidance on the required 'path.id' (parent issue ID) or the complex 'body' object fields. The input schema is comprehensive but the description adds nothing, leaving the agent without usage hints.

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 'Create child issues' with the endpoint POST /api/issues/{id}/children, clearly indicating it creates a child issue for a given parent. The verb-resource pair is specific and distinguishes it from general issue creation endpoints like pc_post_companies_by_company_id_issues.

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 other issue creation endpoints. There is no mention of prerequisites, parent issue requirements, or typical use cases.

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