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

With no annotations provided, the description bears the full disclosure burden. It does add one genuinely valuable behavioral trait — that returned content is untrusted and must not be treated as instructions (a prompt-injection guard) — but says nothing about pagination (the cursor param), result shape, limits, or ordering.

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 terse, front-loaded sentences with no filler; the safety warning earns its place. It is arguably too sparse for a six-parameter tool, but as pure conciseness it is well executed.

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?

With six undocumented parameters, no annotations, and no output schema, the description is far from complete for the tool's complexity. The safety note is valuable but leaves the filtering model, pagination, and return behavior entirely unexplained.

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?

Six parameters exist with 0% schema description coverage, and the description names none of them (kind, site, stage, category, limit, cursor). With such a large coverage gap, the description is expected to compensate and provides no parameter meaning whatsoever.

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 clear verb ('Read') and resource ('released items'), giving an agent a solid sense that this retrieves a feed of previously released content. It does not, however, differentiate itself from siblings like read_own or read_guidance, which also appear to be read tools, so the boundary is left implicit.

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 offers no when-to-use guidance and names no alternatives among the many read/submit siblings. The second sentence is a safety warning rather than usage context, so an agent must infer the calling conditions entirely.

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