get_page_info

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

With no annotations, the description carries the full burden. It does list the returned data fields and implies a read-only operation via 'Get', but it does not disclose how tab_id affects behavior, possible error conditions, or whether any waiting is involved. This leaves important operational aspects unexplained.

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, front-loaded with the action verb, and enumerates all returned properties without filler. There is no wasted or redundant wording.

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 missing tab_id semantics, lack of any output schema, and absence of usage guidance mean the tool cannot be invoked with confidence. An agent must guess the parameter's meaning and the return structure, despite the clear field list.

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 lists a single optional tab_id with no description (0% coverage), and the tool description never mentions this parameter. The agent cannot tell whether tab_id is required, what it identifies, or how it relates to the 'current page'.

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?

States a specific verb ('Get'), a resource ('current page'), and a precise list of fields: URL, title, loading status, scroll state, interactivity, and CAPTCHA presence. This clearly differentiates it from content-focused siblings like get_page_content, though it does not name a sibling explicitly.

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?

Provides no information on when to use this tool versus alternatives such as get_page_content or read_page, no prerequisites, and no mention of the optional tab_id behavior. The only implication is 'when you need page info,' which is weak guidance.

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