List comments

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the implicit behavioral hint that results are limited to scheduled comments for one post — it says nothing about ordering, pagination, or whether non-scheduled comments are excluded.

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?

Extreme brevity here is under-specification, not conciseness: a single four-word fragment that omits the action entirely. There is nothing to front-load because almost no information is present.

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 0% schema description coverage, no output schema, and no parameter explanations, the definition leaves essential gaps for an agent — most critically what the status filter does and what the returned set represents. The annotations cover safety but not semantics.

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% for 2 parameters, so the description carries the full burden — yet it only vaguely implies postId ("for a post"). The status enum (pending/published/failed) is never explained, nor whether it filters scheduled comments by delivery state.

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 text is a noun fragment, "Scheduled comments for a post," with no verb stating that it lists or retrieves anything. It adds a modicum of scope beyond the name (scheduled-only, per-post) but does not distinguish it from siblings like get_comment or list_inbox.

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?

There is no statement of when to use this vs get_comment (single comment), list_inbox (inbox items), or create_comment/schedule-like flows. The agent must infer usage purely from the tool name and the presence of a postId requirement.

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