find_by_placeholder

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to state what happens if no input with the given placeholder exists, whether the tool is read-only, or what the return value is. The name implies a search, but behavior is unclear.

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 (4 words). While brevity is valuable, this is too short to be informative. It sacrifices necessary details that an agent needs to use the tool correctly.

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 that an output schema exists (but is not shown), the description should at least hint at what is returned. It does not. The tool is among many similar find_ tools, and without mentioning return type or side effects, the description is insufficient for an agent to invoke it confidently.

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 input schema has 0% description coverage, and the description adds no extra meaning beyond the parameter name 'placeholder'. The schema already shows it's a required string; the description does not explain what format the placeholder text should be in or whether it supports partial matches.

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 'Find input by placeholder' clearly identifies the verb (find) and resource (input by placeholder). It distinguishes from sibling tools that find by other attributes (label, role, text). However, it lacks specificity about what 'find' entails (e.g., does it return the element, focus it, or click it?).

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?

The description provides no guidance on when to use this tool versus alternatives like find_by_label or find_by_text. It does not mention any prerequisites, exclusions, or typical use cases.

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