add_component

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

With no annotations provided, the description carries the full burden. It explains the tool creates one or more components, supports single and batch modes, and returns a confirmation with component ID(s). It does not mention permissions, validation, or overwriting behavior, but for an add tool it is reasonably transparent.

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 well-structured with a summary, Args list, and Returns. However, the opening lines are somewhat redundant ('Add a new component' and 'This tool adds one or more components' repeat the same idea), and the Args list largely repeats schema descriptions. Still, it's reasonably concise and organized.

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 an 8-parameter tool with two modes, the description provides enough context to invoke it correctly: it explains single vs batch, required fields in single mode, and the return value. It doesn't address edge cases or error handling, but with an output schema available, it is largely complete.

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 schema already documents all 8 parameters with 100% coverage, so baseline is 3. The description adds value by clarifying that name and type are required for single-item mode (schema has no required fields), and by explaining the batch behavior via items. However, it includes a phantom 'ctx' parameter not present in the schema, which is a minor flaw.

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 'Add a new component to the architecture' and further explains it adds one or more components. The verb 'add' and resource 'component' are explicit, and the batch note distinguishes this from update/delete/list sibling tools.

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 explains when to use single-item vs batch mode using the 'items' parameter, providing clear context for both paths. However, it doesn't explicitly mention alternatives like 'use this for creating, not updating components' or exclusions, so it lacks explicit when-not guidance.

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