terminal_get_binding

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

With no annotations, the description carries the behavioral burden. It does convey that the operation is a non-mutating 'Return' and that it reveals 'current effective permissions,' which is useful context beyond the bare tool name. However, it omits prerequisites, error behavior, and what exactly 'metadata' includes.

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, front-loaded sentence with no filler or redundancy. Every word contributes to the core meaning, though its brevity leaves some contextual gaps.

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 tool has no output schema and no annotations, so the description must compensate for that missing context, but it only states the return surface ('binding metadata and current effective permissions'). It does not explain how the binding argument should be specified, what the returned metadata structure is, or how 'effective permissions' are represented, leaving the description incomplete for reliable invocation.

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 only parameter, 'binding', has 0% schema description coverage, and the tool description never mentions the parameter or its expected format. An agent receives no help understanding what value to provide for 'binding' beyond the schema's type and title.

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 uses a specific verb ('Return') and a clear object ('binding metadata and current effective permissions'), so an agent can tell this is a read operation for a single binding's details. It does not explicitly contrast with terminal_list_bindings, but the singular 'binding' plus the 'get' naming implies a targeted lookup rather than a list.

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 about when to use this tool versus siblings like terminal_list_bindings, terminal_bind, or terminal_unbind. The description only states what the tool does, not when it should be selected or when an alternative would be more appropriate.

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