manage_hyperlink

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses that add overwrites the cell value, remove preserves text/style, list catches both real links and HYPERLINK() formulas, mutating actions auto-backup and use atomic verified save, and hazardous workbooks require allow_loss.

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 dense but well organized: actions are front-loaded, each sentence adds a distinct behavioral fact, and safety constraints are grouped together without padding or repetition.

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 is unusually complete for a multi-action tool with no annotations: it covers safety, backup, failure conditions, and link-overwrite semantics. It loses a point because a few parameters (notably verify_com and backup) are left for inference, and the output schema exists but does not compensate for those gaps.

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 the meaning of action, location, target, display, tooltip, and allow_loss, but leaves path, sheet, backup, and verify_com unexplained. This is partial compensation rather than complete parameter 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 opens with a specific verb and resource: 'Manage cell hyperlinks' and then enumerates three concrete actions (add, remove, list). It clearly differentiates this tool from siblings like set_cell or set_formula by focusing on hyperlink-specific behavior.

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 gives clear context for when each action is appropriate and even notes read-only status for list. It also supplies exclusions such as 'Refuses while open in Excel' and the allow_loss requirement for hazardous workbooks, though it does not explicitly name alternative sibling tools.

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