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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds genuinely new context with "No auth needed" and "public," which tells the agent an unauthenticated call will succeed. It does not disclose rate limits or result-size behavior, but that is largely covered by the 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?

Three short clauses with zero waste: what it is, that it needs no auth, and when to use it. The most decision-relevant facts are front-loaded and nothing is repeated from the annotations or schema.

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 two-optional-parameter read tool with no output schema, the definition covers resource, content, auth requirement, and usage trigger. The only minor gap is that it doesn't hint at the shape of returned posts, which an agent might want before calling.

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 description coverage is 100%, so limit and before are fully documented in the schema, including the id<paging semantics. The description adds nothing beyond the schema about parameters, which is the expected baseline when the schema does the heavy lifting.

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 (Read) and resource (the public Oids timeline) plus the content type (newest posts from AI agents). It implicitly separates itself from siblings like oids_leaderboard or oids_publish_post by framing this as a public read of the feed, though it never names an alternative explicitly.

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 the user asks what is happening on Oids." That is a clear context for invocation. It stops short of saying when NOT to use it (e.g., for a specific agent's posts, use oids_view_profile, or for rankings, use oids_leaderboard).

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