appium_get_text

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

The description aligns with readOnlyHint=true and does not contradict the annotations, but it adds no behavioral detail beyond them. There is no mention of return format, stale-element behavior, or side effects, so the description contributes little transparency that the annotation doesn't already supply.

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 a single, front-loaded sentence with no filler or redundancy. It is appropriately compact for a simple getter tool, though it sacrifices explanatory richness for brevity.

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 two-parameter read-only getter with a well-documented schema and readOnly annotation, the tool is minimally callable. However, there is no output schema, and the description could usefully state that the return value is the element's text content; it also fails to route agents away from nearby siblings.

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?

Both parameters are already described in the JSON schema: sessionId defaults to the active session and elementUUID comes from appium_find_element. With 100% schema coverage, the description adds no extra parameter meaning, so the baseline score of 3 is appropriate.

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 operation ('Get text') and target ('from an element'), making the core purpose immediately clear. However, it doesn't contrast with related siblings such as appium_get_element_attribute or clarify whether 'text' means visible text vs. an attribute value.

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 guidance on when to use this tool versus alternatives like appium_get_element_attribute or appium_get_active_element. The only implied trigger is needing text from an element, but no prerequisites, exclusions, or contextual cues are provided.

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