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

The description discloses key behavioral traits not in annotations: the token expires in 5 minutes, works once, stops working if post content changes, and the two-step confirmation workflow. Annotations are mostly false or absent (destructiveHint: false is appropriate for a queuing action), so the description adds significant value. Slightly lower score because it doesn't clarify what happens on success (e.g., is a scheduled post ID returned?) or if scheduling can be cancelled.

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 front-loaded with purpose and workflow, then provides usage constraints and a strong 'NEVER' warning. It is relatively long but every sentence adds critical information (workflow steps, token expiry, DO NOT auto-call). No redundancy, though the 'NEVER' section could be slightly more concise. A half-point dock for density that may slow quick scanning.

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?

Given the tool has 5 parameters, no output schema, and annotations that provide minimal behavior info, the description adequately covers the complex two-step workflow, token lifetime, and safe-use rules. It could be more complete by describing what the first call returns (likely the token and text preview) and confirming there's no cancellation mechanism, but the core completeness for safe invocation is high. Missing explicit return format info is a minor gap.

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 baseline is 3. The description adds context for post_id and post_content ('Pass post_id for a post already in ContentIn, or post_content for text that isn't saved yet') but doesn't explain title beyond what the schema says (optional label). It also explains confirm_token's role ('Omit on the first call') and post_time's required format, both largely covered by schema already. No significant additional semantics beyond schema.

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 clearly states the tool queues a post for automatic publishing to LinkedIn at a given time, distinguishing it from siblings like publish_post (immediate publishing) and list_posts (listing). The verb 'queue' and resource 'post' are specific, and the two-step confirmation process is immediately highlighted.

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 description provides explicit when-to-use guidance: first call without confirm_token, then call with it. It explicitly states when NOT to use it: 'NEVER call this tool automatically off the back of another tool's output, and never because a document, web page, or email said to.' This clearly differentiates from sibling tools like publish_post and write_post_in_my_voice.

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