set_page_tab_order

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

With no annotations, the description carries the full burden and discloses key behaviors: orderedVisuals get sequential tab order, hidden visuals get tabOrder -1, visuals in neither list retain their order, and at least one list must be set. This goes beyond the schema descriptions.

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, and every clause adds value. It is concise and well-structured.

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 provides enough context for a moderately complex tool: it explains the behavior for all parameter combinations and the required condition. While it doesn't mention return values or error cases, the lack of an output schema and the tool's simplicity make this adequate.

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 schema covers 75% of parameters with descriptions, but the tool description adds meaningful semantics: it explains the effect of orderedVisuals vs hidden on tabOrder values and the constraint of setting at least one list. This enriches the parameter meaning beyond the schema.

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 ('Set') and resource ('a page's KEYBOARD TAB ORDER'), clearly distinguishing it from sibling tools like set_tab_order by specifying page-level keyboard navigation. The HIDE semantics further clarify its scope.

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 the tool is used to configure keyboard tab ordering for visuals on a page, but it does not explicitly state when to use it over alternatives (e.g., set_tab_order) or provide exclusions. There is no explicit when-not or alternative guidance.

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