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

Goes well beyond the annotations: it discloses the exact probe mechanics (unsigned listing plus unsigned read of one existing object, no credentials), the three-valued outcome and the explicit warning that 'unknown' is not safe, the network side effect (one request per reading to the bucket's own host on the caller's behalf), and the auth/ownership constraint. The readOnly/no-state-change claim is consistent with readOnlyHint and destructiveHint=false.

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?

Front-loads what the tool does before the caveats, and every sentence carries information (mechanics, return semantics, side effects, ownership). It is dense and long-ish, but nothing is filler; a slightly tighter grouping of the caveats could improve scanability.

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?

There is no output schema, so the description carries the return-value burden and does so fully by defining public/private/unknown and their safe interpretation. Combined with the side-effect and ownership disclosures, an agent has everything needed to invoke and interpret it correctly.

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 coverage is 100%, so both parameters are already documented, but the description adds real semantics for connectionId: shared connections silently return the same not-found as a wrong id, which the schema does not convey. That is meaningful meaning beyond the structured field.

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?

States a concrete verb and resource ('probes one bucket the way an anonymous stranger would') and immediately distinguishes itself from every sibling, none of which perform an anonymous exposure probe. An agent can pick this tool over list_buckets or get_object_metadata without opening either schema.

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?

Gives a clear applicability condition (owner-only; works only for a connection this account created, never a shared one) and even tells the caller how a shared-connection id will fail. It stops short of naming alternative tools for adjacent questions, but no sibling overlaps meaningfully, so the context is sufficient.

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