gh_add_component

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

Description confirms mutation (adding a component), consistent with readOnlyHint=false, but lacks disclosure of error cases, coordinate bounds, or effect on existing components.

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?

Single concise sentence with key action and context. 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?

Adequate for a simple add operation, but could mention behavior when component name is invalid or canvas is not ready. Output schema exists but not referenced.

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?

Input schema already describes parameters (x, y, name) with basic descriptions; the tool description adds no additional meaning. Schema_description_coverage is 0% but schema itself is informative.

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?

Description uses specific verb 'Drop' and resource 'component' with location 'onto the active canvas', clearly distinguishing it from sibling tools like gh_delete_component or gh_connect_components.

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 on when to use this tool versus alternatives such as gh_place_slider or gh_components_search. No prerequisites or context provided.

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