set_hyperlink

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

No annotations are provided, so the description must convey behavioral traits. It states the cell is styled as a link (blue, underlined) and what happens if display is omitted. However, it does not disclose side effects like overwriting existing cell content or undoability.

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 concise (3 sentences) and well-structured. The first sentence states the purpose, and subsequent sentences add essential details without redundancy.

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 absence of annotations and output schema, the description provides adequate context for a simple tool. It covers URL formats, display behavior, and styling. Minor gaps like error handling or return value are acceptable for this complexity level.

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%, so the description must compensate. It explains url and display parameters with examples and behavior, but cell and session_id parameters are not described. Thus, partial 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 'Turn a cell into a hyperlink,' specifying the verb and resource. It distinguishes from siblings like set_formula or write_cell by detailing hyperlink-specific behavior (internal/external URLs, display text, styling).

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 explains when to use the tool (to create hyperlinks) and provides guidelines on URL formats (external vs internal with '#') and display parameter behavior. However, it lacks explicit differentiation from alternatives like set_formula or when not to use it.

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