Get detailed Reddit posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that posts come with platform-side metadata (subreddit, flair, score), which is useful, but it does not disclose pagination, ordering, or any limitations beyond that. No contradiction with annotations.

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 description is short but poorly structured. The first sentence about posting unavailability is a distraction that belongs in a separate operational note, not the tool description. The second part is a fragment lacking a clear verb, and the overall flow is disjointed.

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 simple read tool with an output schema, the description still fails to clearly state its function. It leaves out an explicit statement of what it retrieves and does not explain the limit parameter. The unrelated warning further detracts from completeness. An agent could misinterpret the tool as related to publishing.

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 only 50% (profile is documented in schema, limit is not). The description adds a hint that posts are 'published from a profile,' which maps to the profile parameter, but it provides no explanation of the limit parameter or its default behavior. It does not adequately compensate for the missing schema description.

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 implies the tool returns recent Reddit posts from a profile with metadata, but it lacks an explicit verb and is framed as a noun fragment. The opening sentence about Reddit posting being unavailable is unrelated to this read tool and confuses the purpose. It does not distinguish the tool from siblings like get_history or get_media.

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?

No guidance on when to use this tool versus alternatives. The only directive, 'Do not use reddit as a publish target,' pertains to publishing, not fetching posts, and is irrelevant to this read operation. No context for choosing this over other get tools is provided.

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