get_text_content

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

No annotations exist. Description does not disclose key behaviors: whether it returns text of first matching element, behavior on not found, error handling, or timeout effects. Minimal transparency.

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?

Two lines of Chinese text are extremely concise. Content is front-loaded with the main purpose. Could be longer but is 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?

Given no output schema and simple structure, description falls short: no return format, error handling, or behavior with multiple elements. Leaves agent guessing.

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. Description adds basic info for each parameter (selector is CSS/XPath, timeout is milliseconds), but lacks depth like acceptable selector patterns or timeout behavior.

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 tool retrieves text content of an element, using a specific verb and resource. It distinguishes from sibling tools like get_element_attribute, but could be more explicit.

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 vs alternatives like wait_for_selector or get_element_attribute. No prerequisites or context provided.

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