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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing on top of that: no note about credit cost, cache behavior, or what happens with the optional metrics fetch. Four words contribute zero behavioral context.

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?

Breathlessly short at four words, but this is under-specification rather than efficiency. Nothing is front-loaded because there is nothing to front-load; it wastes the opportunity to state scope.

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 values needn't be described, but for a tool with an optional credit-costing param and numerous close siblings, the description is far too thin to let an agent confidently choose and invoke it.

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 the schema already explains both 'id' (id or comments URL) and 'include_metrics' (credit cost, what it fetches). Baseline 3 applies; the description adds nothing beyond the schema but 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?

"Reddit post details" is essentially a restatement of the tool name with no specific verb or scope. It does not distinguish this single-post fetch from siblings like reddit_subreddit_posts, reddit_comments, or reddit_search beyond the implicit 'post' resource.

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 when-to-use guidance, no mention of alternatives (reddit_comments for replies, reddit_subreddit_posts for listings), and no preconditions. The agent is left to infer everything from the name.

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