List scheduled posts

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

The readOnlyHint annotation already establishes a safe read, but the description adds the key behavioral constraint that only local queue posts are shown, not those in LinkedIn's native scheduler. It also mentions that status is included in the output, which is useful. No contradictions with the annotation.

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 two concise sentences with the core purpose front-loaded and the important limitation immediately following. Every word earns its place.

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 list tool with one optional parameter and no output schema, the description covers the core functionality and the main boundary condition. It doesn't describe sorting or pagination, but these are minor for this scope.

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 description does not mention the optional 'status' parameter or that it can filter results, and schema description coverage is 0%. The enum in the schema provides some meaning, but the description fails to compensate for the lack of parameter documentation.

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 ('List') and resource ('queued/scheduled posts') and adds a clear scope differentiator ('LOCAL queue only'), distinguishing it from siblings like list_my_posts. The caveat about LinkedIn's native scheduler further clarifies what this tool does and does not cover.

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?

It clearly states when this tool applies: local queue only, and notes that native scheduler posts are 'only visible on linkedin.com', which guides an agent away from using this tool for those posts. It doesn't explicitly name an alternative sibling tool, but the boundary is clear enough.

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