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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, and the description's 'List' is consistent with a safe read operation. The description does not add extra behavioral details such as pagination, ordering, or whether only scheduled-status posts are returned, but the annotations reduce the burden.

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 one concise sentence that front-loads the action and mentions the relevant output fields. Every word earns its place, with no redundant phrasing.

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 one-parameter, read-only list tool, the description sufficiently covers the return fields and implies the prerequisite ID source. The title says 'scheduled posts' while the description says 'posts in a content plan', leaving minor ambiguity about whether all posts or only scheduled ones are included, but overall the definition is adequate.

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?

The single parameter content_plan_id is fully documented in the schema with 'Plan id from list_content_plans', giving 100% schema coverage. The description itself does not add detail about the parameter beyond relating it to 'a content plan', so the baseline score applies.

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 uses a specific verb and resource: 'List the posts in a content plan' with dates, status, and text. This clearly differentiates it from list_content_plans, which lists plans rather than posts, though it does not explicitly name any sibling alternatives.

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?

Usage context is implied through the parameter note 'Plan id from list_content_plans', which signals a prerequisite call. However, there is no explicit guidance about when to use this tool versus alternatives like list_company_posts or schedule_post, so the agent must infer the intended workflow.

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