get_text

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

No annotations are provided, so the description carries the full behavioral burden. It gives no information about read-only behavior, selector requirements, fallback behavior, return format, or error handling, leaving the agent with essentially no behavioral disclosure.

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 short, but it is under-specified rather than concise. Every part of the fragment is present but none of it earns its place by adding useful information beyond the tool name.

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 undocumented parameters, no annotations, no output schema, and many similar siblings, the description is completely inadequate. An agent cannot reliably infer how to invoke it or interpret its results.

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 schema has two parameters (selector required, fallback optional) with 0% description coverage. The description does not explain what selector targets, what fallback does, or when fallback is used, so it fails to compensate for the missing schema documentation.

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 'Get text (alias)' restates the tool name and adds an unclear parenthetical. It does not specify what text is retrieved, from what element or page context, or how it differs from siblings like get, get_html, or get_title.

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?

There is no when-to-use guidance, no alternatives mentioned, and no conditions for selecting this tool over the many sibling retrieval tools. The single word 'alias' does not provide actionable usage context.

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