get_page_info

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

Without annotations, the description must carry behavioral transparency. The verb 'Get' implies a read-only operation with no side effects, but it does not explicitly state that no state changes occur or that it is safe to call at any time. The description provides a basic indication but lacks explicit assurances.

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, concise sentence that efficiently communicates the core function without superfluous details. It is front-loaded with the action and resource, making it immediately clear to the reader.

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 that the tool has no parameters and no output schema, the description is sufficient for an agent to understand what the tool does and when to call it. The phrase 'for targeted tools' hints at a specific use case but does not leave critical gaps in understanding for a simple getter 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?

The tool has no parameters, and the schema coverage for parameters is 100% (none exist). Per the rubric, the baseline score is 3 when there are no parameters to describe, and the description does not add any parameter-related information since there is nothing to explain.

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 action ('Get') and the resources ('page metadata plus a zero-based frame list'), which distinguishes it from sibling tools like 'take_screenshot' or 'reload'. The phrase 'for targeted tools' is slightly vague but does not obscure the primary purpose.

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?

The description does not specify when to use this tool versus alternatives, nor does it mention any prerequisites or contextual conditions. It only states what the tool does, leaving the agent to infer when it is appropriate without explicit guidance.

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