iframe_target

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state what happens if no matching iframe is found (returns null? errors?), whether multiple matches return only the first by document order, or what the targetId is used for. The 'first URL' qualifier hints at non-deterministic selection behavior but doesn't explain it.

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?

Single sentence, efficient. The example call 'iframe_target("player")' is helpful illustrative context. No wasted words, though more substance could fit in the same space.

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 1-parameter tool with no annotations and no output schema, the description is thin. It doesn't explain the return value's use, failure behavior, or relationship to other tab/iframe operations. Given the tool's niche purpose (iframe handling) among many browser tools, more context about when this is valuable would help.

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 0%, so the description must compensate. It only mentions url_substr implicitly via 'URL 含 url_substr' but doesn't clarify matching semantics (exact match vs substring, case sensitivity, URL encoding). No format or type guidance is given beyond the bare schema string type.

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 states a specific verb+resource ('返回' a targetId) and clarifies it finds the first iframe whose URL contains a substring. However, it doesn't clearly distinguish from siblings like find_text or list_tabs, and the purpose is somewhat implied rather than fully specified.

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 guidance on when to use this tool versus alternatives. It doesn't say what 'player' refers to in the example or when an agent would need an iframe targetId. No exclusions or alternative tool references are provided.

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