resolve_uid_to_selector

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

Without annotations, the description adds the behavioral trait 'Fails if stale,' which is helpful. However, it does not disclose the return format (presumably a CSS selector string), error behavior, or side effects. Some transparency is present but incomplete.

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 two short sentences: the first conveys the core purpose, and the second adds a crucial constraint. No extraneous words; every sentence adds value.

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 tool has a single parameter, no output schema, and no annotations. The description covers the basic purpose and a failure condition but lacks details about the output format, definition of 'stale,' and error handling. Adequate for a simple tool but has 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?

The schema already describes 'uid' as 'UID from snapshot' (100% coverage). The description adds meaning by specifying the operation (resolve to CSS selector), which clarifies the parameter's role 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 clearly states 'Resolve UID to CSS selector,' which is a specific verb and resource. It distinguishes itself from sibling tools that use UIDs for actions (e.g., click_by_uid) by explaining it resolves to a selector rather than performing an action.

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 use for resolving UIDs from a snapshot, and notes that it fails if stale, but does not provide explicit when-to-use or when-not-to-use guidance relative to siblings. No alternatives are mentioned.

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