cst_schematic_create_rlc

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

No annotations provided; description mentions connected vs. offline modes but lacks details on side effects, prerequisites (e.g., open project), or error handling. Minimal behavioral context beyond mode descriptions.

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?

Concise two sentences front-loading purpose and key modes. No wasted words.

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?

No output schema; description does not explain return values or success/failure indicators. Missing prerequisites like project state. Adequate for a simple creation tool but could be more 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?

Schema coverage is 100%, so each parameter has a description. The tool description reinforces the 'kind' parameter but adds no new semantics beyond what's in the schema.

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 tool creates a resistor, inductor, or capacitor in a Design Studio schematic. It differentiates from sibling tools like ports or antennas by specifying the RLC component.

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 mentions two modes (connected/offline) but does not provide explicit guidance on when to use this tool versus other schematic creation tools. Implied usage for RLC creation, but no when-not or alternatives.

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