get_page_text

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

Discloses truncation behavior, max_chars parameter, and the truncated flag. No annotations provided, so description carries the burden. Lacks details on waiting for page load or error handling, but adequate for a read operation.

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?

Structured with Purpose, Parameters, Returns sections. Concise but includes all necessary details. Some redundancy (session_id repeated) but overall efficient.

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?

No output schema, but description provides full return structure including truncated, status, message. Covers all relevant aspects for a two-parameter tool. Complete and self-contained.

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 has 0% description coverage; the description fully compensates with clear explanations: 'Active browser session identifier' and 'Maximum characters to return (default: 5000)'. Adds meaning beyond schema.

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?

Explicitly states 'Retrieve visible text from the page body' with clear verb and resource. Sibling tools like get_page_title or get_interactive_elements have different purposes, so it is distinct.

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 context ('reasoning, validation, or extraction') but does not explicitly contrast with sibling tools like get_accessibility_tree or get_interactive_elements. No when-not-to-use or alternative mentions.

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