set_basic_auth

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

Annotations indicate idempotence but not the replacing behavior or clearing method. Description adds that it replaces any bearer token and that empty credentials clear auth, providing valuable behavioral context.

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?

Two concise sentences with no wasted words. All information is front-loaded and relevant.

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 simple two-parameter setter without output schema, the description fully covers behavior, clearing option, and replacement effect. Complete for tool selection and 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?

Schema has 100% coverage with basic descriptions. The description adds nuance that empty values clear auth, which goes beyond schema and helps agent understand how to invoke clearing.

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 explicitly states the tool configures HTTP Basic authentication, replaces bearer tokens, and can clear via empty username/password. This clearly differentiates it from sibling tools like set_auth_token.

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 implies usage when configuring basic auth vs bearer token, and mentions clearing. It lacks explicit when-not or alternative references, but context is clear given sibling tools.

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