zen_page_text

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

No annotations provided, so the description carries the full burden. It explains the basic operation (text extraction) and parameter behavior (default to active tab), but does not disclose potential side effects, permissions, or limitations (e.g., dynamic content handling). It is adequate but lacks deeper behavioral context.

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 concise: a one-line purpose and a brief parameter note. It does not waste words, though the parameter section could be more structured (e.g., bulleted). Overall, it is appropriately sized and front-loaded.

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 tool's simplicity (1 parameter, no output schema), the description covers the main purpose and parameter usage but omits details about return values, error conditions, or edge cases (e.g., empty pages). It meets minimum viability but lacks completeness.

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 description adds meaning beyond the schema by explaining the 'tab_id' parameter's default (active tab) and recommending usage for non-active tabs. However, schema coverage is 0%, so the description must compensate, and it does so effectively with contextual guidance.

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 states 'Extract all readable text from the current page' which is a specific verb+resource. It also distinguishes from the sibling tool 'zen_page_text_by_tab_id' by noting they do the same thing now, clarifying the tool's role.

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?

Explicitly says when to use tab_id (for non-active tabs) and compares with the sibling 'zen_page_text_by_tab_id', advising preference for this tool. This provides clear guidance on tool selection.

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