frame

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

With no annotations provided, the description carries the full burden. It reveals the 'omit both to clear' behavior but does not disclose side effects (e.g., how subsequent operations are affected), what happens if no matching frame is found, or whether this operation requires any session/lease handling. The behavioral disclosure is minimal.

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, tightly worded sentence with no redundancy. The main action and the edge case of clearing are front-loaded. It earns its place with zero waste.

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 simple state-switching tool, the description covers the core function but misses details like what happens when both name and url are specified (which takes precedence) or the behavior when no frame matches. With a simple schema and no output schema, a bit more completeness could be expected, but it is adequate for a basic switch operation.

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 description coverage is 100%, so the baseline is 3. The tool description matches the 'name' and 'url' parameters but adds no additional semantics, such as precedence when both are provided or how they interact. The lease and session parameters are not mentioned in the description, though the schema fully documents them.

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 verb 'Switch', the resource 'active frame', and the method 'by name or URL substring'. It also notes the clearing capability, which distinguishes it from the 'frames' listing tool. The purpose is immediately clear and unambiguous.

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 is given on when to use this tool versus alternatives. It does not mention any conditions for use, exclusions, or refer to sibling tools like 'frames' or 'page_switch'. The description simply states the operation without contextual routing.

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