find_textbox_by_value

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

Discloses search scope (Body/PageHeader/PageFooter), behavior for multiple matches ('surfaces once per match'), and return format ('[textbox, value, region]'). No annotations present, so description carries full burden.

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?

Three sentences, front-loaded with core action, no unnecessary words.

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, description explains return shape and matching behavior. Sufficient for an AI agent to understand tool purpose and output.

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?

Two parameters: 'path' and 'pattern'. Schema description covers 50% (only pattern described as 'Python regex (re.search)'). Description adds no further info on 'path' or usage meaning beyond the schema.

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?

Description states specific verb 'Find' and resource 'Textbox' with criteria (value matching regex). Distinguishes from sibling 'find_textboxes_by_style' which searches by style.

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?

Provides explicit use case: 'finding stale =Parameters!Old.Value references after rename_parameter' and 'any cross-cutting expression edit'. Implies usage context but does not exclude when not to use or list alternative tools.

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