resolve_uid_to_selector

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

The description mentions that the tool 'Fails if stale,' which is a behavioral trait. However, with no annotations provided, the description should disclose more details such as error handling, return format, or side effects. The single sentence is insufficient.

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 very short (two sentences) and front-loaded, conveying the core functionality efficiently. However, it could benefit from a bit more structure to include return value explanation.

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 tool's simplicity (single parameter, no output schema), the description covers the basic purpose and a failure condition. However, it omits what the tool returns (presumably a CSS selector string) and lacks examples or context for usage beyond the failure note.

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% with the parameter 'uid' described as 'UID from snapshot'. The description adds no further meaning beyond the schema, so baseline score of 3 is appropriate.

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 the tool's purpose: resolving a UID to a CSS selector. It uses a specific verb ('Resolve') and resource ('UID to CSS selector'), and distinguishes itself from sibling action tools like click_by_uid.

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 explicit guidance on when to use this tool versus alternatives. While it is unique among siblings, the description does not indicate prerequisites, typical use cases, 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.