bind_tcp_timeouts

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

Annotations already declare readOnlyHint=true, so "[READ]" and "without changing them" largely restate structured data rather than adding to it. Nothing is said about whether timeouts are global or per-target, what units or defaults apply, or what the response looks like for a tool with no output schema.

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, front-loaded with the [READ] marker and the resource name; nothing is padded or redundant within the sentence itself. It is arguably too terse rather than too long.

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 read tool this is close to adequate, but the sole parameter is undocumented in both schema and description, and with no output schema the agent has no idea what the return shape or the meaning of "target" is. The definition leaves a real gap before the tool can be invoked confidently.

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 is one optional parameter, "target", with 0% schema description coverage, and the description says nothing about it at all — not whether it is a server, view, zone, or address. With low coverage the description is expected to compensate, and it does not.

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?

Specific verb plus resource: "Show current DNS TCP timeouts" tells the agent exactly what is returned, and "[READ]" plus "without changing them" pins the operation as non-mutating. It is reasonably distinguishable from siblings like bind_fetch_limits or bind_status, though it never explicitly contrasts itself with them.

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 the usage context (inspecting timeouts, not altering them) but gives no explicit when-to-use, when-not-to-use, or named alternative among the many bind_* status tools. An agent can infer it is a safe inspection call, but routing between it and e.g. bind_fetch_limits is left to guesswork.

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