gh_place_slider

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

Annotations indicate readOnlyHint is false, consistent with the create action. The description adds value by stating the return of component_id for further operations. No contradictions.

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 primary action, efficient and to the point. No unnecessary 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?

The description covers the core purpose and return value, but given the complexity of the input schema (7 parameters), it does not explain all options. The output schema exists but is not described, though the description mentions component_id. Incomplete for a parameter-rich tool.

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 description coverage is 0% – the tool description does not elaborate on parameters. The schema itself provides detailed descriptions, but the tool description only vaguely mentions 'bounds and initial value,' which partially compensates but is insufficient for a multi-parameter tool.

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 Number Slider with bounds and initial value, and distinguishes itself from sibling tools like gh_connect_components and gh_set_slider by mentioning that the returned component_id can be used for subsequent calls.

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 by noting that after placing the slider, you can use gh_connect_components or gh_set_slider to target it. However, it does not explicitly exclude alternative tools or state prerequisites.

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