gh_bind_template_parameter

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

The description states 'Set', aligning with the readOnlyHint=false annotation, but adds no additional behavioral details. It does not disclose potential side effects, required template state, or the return value.

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 a single sentence with no redundant information. It is concise and front-loads the core purpose.

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?

Given the tool's complexity (1 required param containing 3 sub-params) and the presence of an output schema, the description lacks completeness. It omits preconditions, error handling, and the nature of the return value, leaving gaps for the agent.

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%, yet the description does not elaborate on the parameters beyond calling them 'single named parameter'. The schema's own descriptions are minimal but present. The description fails to compensate for the low coverage.

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 verb 'Set' and the resource 'single named parameter on a loaded template'. It specifies the template types (slider/panel/toggle), which distinguishes it from sibling tools like gh_set_slider, gh_set_panel, and gh_set_toggle that operate on components directly.

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 is provided on when to use this tool versus alternatives, such as after gh_load_template or in place of direct parameter setters. The agent is left to infer the usage context.

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