add_solution_component

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

Beyond the annotations, the description discloses that preview is default, that validation covers object/type, CSDL and membership/dependency baseline, that parent shells may still be added, and that execution requires an explicit unprotected Action. It adds substantial behavioral context, though it does not fully spell out permissions or irreversible effects.

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 dense but front-loaded and appropriately sized for a complex, destructive 14-parameter tool. Every sentence carries relevant information, though the single-paragraph format and heavy jargon reduce readability slightly.

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 complex mutation tool with no output schema, the description covers preview versus execute, validation scope, component types, conditional logical_name, fixed flags, implicit parent additions, and post-execution verification. It still leaves minor gaps around permissions, how planHash is obtained, and exact preview output.

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 adds meaningful parameter context beyond the schema, especially the component type code mapping (1, 2, 9, 10, 14, 26, 60, 61, 90–93) and the conditional requirement that Attribute/Key requires logical_name. Schema coverage is 57%, and the description compensates for the missing enum and conditional-requirement details.

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: adding one existing component to a visible ordinary unmanaged solution, with preview as the default mode. It is clear what the tool does, though it does not explicitly name sibling tools like list_solution_components as alternatives.

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?

It gives a clear usage protocol: preview by default, then execute with planHash plus an explicit unprotected Action, followed by rereading membership and reporting deltas. It does not explicitly state when not to use the tool or name alternative siblings, so it falls short of a 5.

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