get_user_agent

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

Annotations are absent, so the description carries the behavioral disclosure burden. The verb 'Get' clearly indicates a non-mutating read operation, and the zero-parameter design reduces risk, but no explicit statement is made about side effects, browser-session requirements, or failure modes.

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 no filler, restatement, or redundant detail. Every word adds semantic value.

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?

For a zero-parameter getter with an output schema available, the description covers the essential context: what is returned and that it reflects the current browser. No additional usage conditions or alternatives are necessary for correct invocation.

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?

There are no parameters and the schema already declares an empty object with 100% coverage, so no parameter documentation is needed. The description reinforces that the output concerns the user agent string, which is enough for a parameterless tool.

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 'Get the browser's current user agent string' uses a specific verb (Get), a specific resource (the user agent string), and a scope qualifier (current browser). It is immediately distinguishable from all sibling getters because no other tool targets the user agent.

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?

No explicit when-to-use or exclusion guidance is provided, and no alternative sibling exists for fetching the user agent. The intended usage is implied by the description: call this tool when the current user agent string is needed.

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