get_text_content

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

With no annotations provided, the description carries full responsibility. It only mentions a pagination contract (implying paginated results) and 'visible' text, but does not disclose whether hidden text is included, performance characteristics, or any constraints. This is insufficient for an agent to understand the tool's behavior.

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 extremely concise—one sentence that conveys the core purpose and a key behavior reference. Every word is functional; no unnecessary content.

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 presence of an output schema (not shown) and 0 schema description coverage, the description is too sparse. It lacks details on what 'visible page text' includes, pagination specifics, and how the output is structured. More completeness is needed for reliable tool usage.

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 should explain parameters. However, it does not describe offset or max_chars, only cryptically referencing a 'pagination contract' that assumes prior knowledge. The agent gains no additional meaning beyond the parameter names.

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 visible page text') and the resource ('page text'). However, it relies on reference to another tool ('same pagination contract as get_content') without explaining what get_content does or how this tool differs from it, which slightly reduces clarity for agents unfamiliar with get_content.

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?

No guidance on when to use this tool versus alternatives like get_element_text or get_content. The description merely notes a similarity in pagination contract but does not indicate situations where this tool is preferable.

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