User agent parse

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

While annotations provide safety hints, the description adds critical operational behavior by listing the specific types of bots and clients it recognizes (e.g., Googlebot, curl, Postman), defining its scope far beyond basic parsing.

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?

Although long, the definition is entirely efficient. Every sentence adds unique, high-value information regarding the parsing capabilities and input flexibility.

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 complex, multi-mode nature of the tool, the description is perfectly complete. It covers what it does, what it extracts, what formats it handles, and its performance limitations.

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 schema coverage is 100%. The description supplements this by explaining how to use the input fields—specifically that a 'file' can be a path or a base64 string, and how the 'accessLog' flag dictates log processing behavior.

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 purpose is exceptionally clear, specifying that it 'Parse[s] browser user-agent strings' and detailing the exact fields extracted (browser, engine, OS, device type, vendor, model).

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?

It provides multiple usage paths: single user agent, list, file path, and parsing an access log. It also explicitly defines operational boundaries, noting 'up to 5000 per call.'

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