httpbin_user_agent

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered elsewhere. The description adds nothing beyond restating the resource: it never notes that the returned User-Agent is the MCP server's HTTP client identity rather than the end user's browser, which is the one non-obvious behavioral fact here.

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?

A single short sentence with the resource front-loaded and no filler. It is terse to the point of omitting useful routing information, but nothing present is wasted.

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 read-only echo endpoint with no output schema, the description is minimally sufficient: it names the returned value. It does not describe the response shape (plain text vs. JSON field) or caveat that the value reflects the calling client, leaving modest gaps an agent could trip on.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify. The statement that it returns 'your User-Agent string' is the only semantic needed.

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 states a specific verb and resource (get the User-Agent string) and names the httpbin backing service, so an agent knows exactly what value comes back. It stops short of distinguishing this from sibling httpbin_headers, which also surfaces User-Agent among other headers.

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 guidance on when to pick this over httpbin_headers, httpbin_get, or httpbin_ip. The agent must infer that this is the narrow single-value variant of the header-inspection family.

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