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

Adds substantial context beyond readOnlyHint/destructiveHint: it declares no new job creation, no institution call, no publishing, no quota consumption, and defines uniform not-found semantics for missing, expired, deleted, or other-owner refs. The opening auth sentences are muddled ('No credential or login required' followed by 'XBOSS 인증은 필요합니다'), which slightly clouds the access model.

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 core purpose sentence is buried in fourth position behind auth boilerplate, and the same point is made twice: 'No credential or login required' and 'institution logins or credential registration are not required'. The safety and error-semantics sentences do earn their place, but the preamble is redundant.

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 one-parameter read with annotations covering the safety profile and no output schema, the description covers auth, side effects, scope limits, and failure modes well. The one remaining gap is any hint about the shape or size of the returned body.

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% on a single parameter, so the schema already carries the type, pattern, length, and value-source guidance. The description adds a small amount (the ref is what identifies the body in this connection) but largely restates the schema's instruction to pass the prior response's value verbatim.

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 specific verb and resource: read a previously archived body identified by content_artifact_ref within this connection. It also scopes what is readable (only originals belonging to this connection's org and environment), which pins the tool down against the sibling xdata__job__result.

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 an explicit trigger ('use when verifying the original before resuming the task after blog reconnection') and a clear anti-pattern ('if the prior institution write result is unclear, do not re-upload the body or auto-resend the write'). It never names a specific alternative tool, so routing is implied rather than spelled out.

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