add_template_child

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

Annotations offer limited behavioral info. The description discloses the return value (child template ID) but lacks details on prerequisites (e.g., template must exist), side effects, or permission requirements. No contradiction with annotations.

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?

Two sentences, front-loaded with the action and resource. No unnecessary words; every sentence serves a purpose.

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 complexity (8 parameters, 3 required) and schema richness, the description is reasonably complete. It covers purpose and return value, though it could mention error cases or prerequisites.

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?

With 88% schema coverage, the schema already describes most parameters. The tool description adds value by explaining the 'child' concept and return value, which goes beyond schema descriptions.

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 action ('Add'), the resource ('child template to an issue template'), and its purpose (defining default values for sub-issues). It distinguishes from siblings like 'create_issue_template' and 'remove_template_child'.

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 implies when to use this tool (when adding a sub-task template) but does not explicitly exclude alternative tools or provide when-not-to-use guidance. Siblings like 'remove_template_child' provide contrast.

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