detect_login_form

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

No annotations are provided, so the description bears the full burden of disclosing behavior. It only says 'provide structured information' without detailing what that structure looks like, whether it is read-only, or how it handles multiple/absent forms. The lack of behavioral detail is a significant gap.

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 a clear verb and object. The emoji 🆕 adds irrelevant flourish but does not detract from the message. No wasted 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 the lack of an output schema and annotations, the description is somewhat thin. It identifies the main function but omits details about return format, behavior when no login form is found, and whether it works on the current page or across the site. These details would provide better completeness for an agent.

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 tool has zero parameters, which sets a baseline of 4. The description doesn't need to explain parameters but does hint at the output nature (username/password fields), which adds slight semantic value beyond the empty 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?

The description clearly states the tool's purpose: 'Auto-detect login forms and provide structured information about username/password fields'. It uses a specific verb (auto-detect) and resource (login forms), and the focus on username/password fields differentiates it from sibling detection tools like detect_popups, detect_ads, and detect_captcha.

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?

Usage context is implied: use this when you need login form detection. However, no explicit guidance is given about when to prefer this over related tools like get_form_analysis or smart_fill_form, nor are any exclusions mentioned.

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