check_focus_visibility

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

With no annotations available, the description carries the full burden of behavioral disclosure, but it only says 'Check...', which doesn't reveal whether it's read-only, what it returns, what side effects occur, or what 'focus signals' refers to. This is a severe transparency gap for an agent invoking the tool.

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 extremely brief, but this is under-specification rather than conciseness. It lacks any supporting structure or additional details, making the brevity unhelpful.

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 absence of annotations, output schema, and parameter descriptions, the tool is woefully underspecified. The description contributes almost nothing to the agent's understanding of how, when, or with what parameters to invoke the tool.

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% and the description does not mention taskId or pathname at all. It fails to explain what these parameters mean, whether they are required, or how they influence the check, leaving the agent without any guidance on invocation.

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 'Check visible focus signals' is terse and uses vague jargon ('focus signals') without clarifying whether it's an accessibility check, UI state inspection, or something else. It doesn't differentiate from sibling tools like run_accessibility_check or test_keyboard_navigation, so its purpose remains ambiguous.

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 usage context is provided. The description doesn't say when this tool should be used, what prerequisites exist, or how it compares to alternatives. The sibling list contains many similar-sounding tools, but this description offers no selection criteria.

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