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

Beyond the read-only annotations, the description discloses authentication requirements, organization/environment scoping, absence of publication or usage deduction, and the fact that missing, expired, deleted, or foreign-owned references all return not found. It also adds operational safety guidance about not re-uploading or auto-resending writes.

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 content is useful but not tightly front-loaded: it opens with authentication caveats, and the central purpose appears only after several sentences. Authentication is stated three times in slightly different forms, and the non-creation of new tasks is repeated at the end.

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 tool with full schema coverage and read-only annotations, the description covers the necessary authentication context, access scope, side-effect exclusions, failure semantics, and when to use it. No output schema exists, and the description provides enough behavioral context for correct 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 coverage is 100%, so the basic meaning of content_artifact_ref is already documented. The description adds useful meaning beyond the schema by explaining that only content belonging to this connection's organization and environment is readable and that missing or foreign references resolve to not found.

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: it verifies the previously stored body/content via content_artifact_ref. It also scopes the read to original text belonging to this connection's organization and environment, which clearly distinguishes it from write, publish, or institution-call tools.

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?

It gives an explicit usage moment: verify the original text before resuming the original task after reconnecting the blog. It also warns not to re-upload content or automatically resend writes when a prior institutional write result is unclear, though it does not name a sibling alternative such as job result retrieval.

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