choose_field_first_row

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action of opening a form and pressing a button, but omits any side effects, whether it is a read or write operation, or what happens after the button press. This is minimal 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 a single sentence, which is short, but it is under-specified rather than concise. It lacks essential details about parameters and usage, making it too thin to be effective.

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 three parameters, no annotations, and no output schema, the description is extremely incomplete. An agent would not know what field_name refers to, what session_id represents, or how search_by_title affects behavior, making it nearly impossible to call 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 0%, meaning the description provides no explanation of any parameters. The field_name, session_id, and search_by_title parameters are not described at all, leaving their purpose and expected values entirely ambiguous.

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 clearly states the action: opening a reference selection form and pressing its standard Choose button. It names the verb and resource, but it doesn't explicitly differentiate from sibling tools like choose_field_from_list or choose_current_row, which might perform similar selection actions.

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 tells what the tool does but offers no guidance on when to use it versus alternatives. It doesn't mention prerequisites, such as an active form, or when a different tool like choose_field_from_list would be more appropriate.

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