List Posts

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

Annotations already declare readOnly, idempotent, and open-world behavior, so safety is covered. The description adds real context beyond them: results are ordered by recent activity, each summary carries only a short snippet, and full content requires a different call. It does not mention pagination behavior, though limit/offset exist.

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?

Front-loads the one-line purpose before drilling into filter/folder semantics, then closes with the escalation pointer. Dense but every sentence does work; the filter block is a little list-like but not wasteful.

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?

An output schema exists, so return shape needn't be restated, yet the description usefully warns the summaries are snippet-only. With annotations covering safety, the only real omission is the meaning/defaults of limit and offset.

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 0%, so the description must carry the load. It does well on filter (seven modes enumerated and explained, except the default "all") and folder (with an example), but says nothing about limit, offset, or course syntax. The remaining gaps cap it at a solid-but-incomplete 3.

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 ("List post summaries for a course") plus scope and ordering ("most recent activity first"). It clearly distinguishes itself from siblings get_post/get_posts, which it says return "full threads" instead of summaries.

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?

Explicitly routes the agent: enumerates what each filter value selects, explains the folder constraint, tells the agent that list_courses reveals folder names, and names the alternatives (get_post/get_posts) for complete threads. The when-to-use boundary is unambiguous.

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