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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description earns credit for adding behavioral edge cases: missing/unavailable IDs return not_found per item, duplicate IDs are normalized, and default content excludes prices. This goes beyond a generic read operation.

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?

Four sentences, each carrying a distinct piece of information: purpose, default projection content, missing-ID handling, and duplicate normalization. No filler, with the primary purpose front-loaded.

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 2-parameter batch reader with no output schema, the description covers the batch limit, missing-item behavior, duplicate normalization, and default return content. It omits only minor details like exact response format or explicit market projection output, which are not essential for a basic call.

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 clarify the parameters. It identifies post_ids as the batch input and describes what the 'reading' projection returns, but it does not explain the 'market' projection's output. It adds some meaning beyond the schema but does not fully compensate for the coverage gap.

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'), a defined resource ('selected post IDs'), and a batch scope ('up to 50 ... in one batch'). This clearly differentiates the tool from the singular sibling get_post and from aggregate/search tools.

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?

The 'in one batch' phrasing implies the intended use case: reading many known IDs at once. The default reading vs. market projection hints at routing price-related queries elsewhere, but no sibling is named explicitly and no exclusion criteria are stated, leaving boundary decisions to inference.

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