get

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. The description only states the action but doesn't specify if the tool is read-only, requires a prior snapshot, or has any side effects. The agent cannot infer safety or prerequisites from the description alone.

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, concise sentence with no extraneous words. It is front-loaded and efficient, earning its place without waste.

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 tool's complexity (21 parameters, no output schema) and the absence of annotations, the description is too minimal. It does not explain what 'text' or 'attributes' are returned, how to interpret the output, or how the tool interacts with the device. The high schema coverage partially compensates, but the description lacks essential context for an agent to use the tool correctly.

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 95%, so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides. The parameters are well-documented in the schema, so the description doesn't need to compensate, but it also doesn't add value.

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 element text or attributes' clearly states the verb and resource (element), and it distinguishes itself from sibling tools like 'find' (which locates elements) and 'click'. However, it could be more specific about the scope (UI element) and the exact meaning of 'attributes'.

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 is provided on when to use this tool versus alternatives. For example, it doesn't explain when to use 'get' instead of 'find' or 'snapshot'. There are no when-not-to-use or exclusionary conditions.

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