page_read

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

No annotations are present, so the description carries the behavioral disclosure burden. It does disclose that the output is readable text, includes tables as text, and is truncated to maxChars. It does not mention error behavior, whether a page must be open, or what happens when no page is open, leaving some behavioral gaps.

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 compact and front-loaded, opening with the core action and resource. The truncation note is useful. It is slightly under-specified, but the brevity is not padding or redundancy.

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?

For a tool with no output schema, no annotations, and no parameter descriptions, the description is too sparse to be fully actionable. It omits selector semantics, return format details, and failure behavior. An agent may still use it correctly in simple cases, but significant context is missing.

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 description coverage is 0%, so the description must compensate. It adds meaning to maxChars by noting that output truncates to it, but the selector parameter is completely unaddressed, and maxChars' default/minimum/maximum are left to the schema. This is insufficient coverage for a two-parameter tool with no schema descriptions.

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 a specific verb ('Extract') and specific resource ('currently open portal page'), making the tool's purpose clear. It reads page text, which distinguishes it from sibling tools that retrieve market data or open pages, though it does not name those siblings 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?

The phrase 'currently open portal page' implies the tool should be used after page_open, and before other data tools. However, there is no explicit guidance about when not to use it, prerequisites, or how it compares to alternatives such as get_quote or search_symbol.

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