ui_select_document

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It merely states 'select' without explaining side effects (e.g., does it change UI state, trigger any events, or require a preceding action?). The lack of details on what occurs after selection leaves the agent uncertain about the tool's impact.

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, well-constructed sentence that places the most important information first. Every word is necessary, and there is no redundant or verbose content.

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?

For a UI selection tool with no output schema, the description covers the selection method but omits post-selection behavior (e.g., what the user sees, whether a document detail panel opens). It does not specify if the tool requires a prior list load, which is important for correct sequencing.

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 coverage is 100%, so the base is 3. The description adds minimal value beyond the schema by introducing 'current list' context, but the schema already defines each parameter clearly. The description does not clarify constraints like mutual exclusivity of parameters or default behavior if both are provided.

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 'select' and resource 'document', clearly indicating the action. It further specifies the mechanism 'by ID or index' and context 'in the current list', effectively distinguishing it from siblings like 'open_document_external' or 'list_folder_contents'.

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 does not provide guidance on when to use this tool versus alternatives (e.g., when to select vs. navigate vs. open). It lacks explicit conditions, prerequisites, or examples, leaving the agent to infer usage from the name alone.

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