get_alert_text

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

Describes return text from an open alert, but does not mention timeout behavior or error case when no alert is present. No annotations to supplement.

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 concise sentence, but could be improved by mentioning the timeout parameter.

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?

Mostly complete for a simple getter with one optional param and no output schema. Lacks timeout explanation and error handling details.

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 parameter 'timeout' is not mentioned in the description. Schema has 0% coverage, so description should explain it, but it doesn't.

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?

Clearly states it returns the text from a JS alert/confirm/prompt. Distinguishes from sibling tools like accept_alert and dismiss_alert which perform actions.

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?

Implied usage when needing to read alert text before handling it, but no explicit guidance on when to use vs alternatives or what happens if no alert is present.

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