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

Annotations already declare safe, idempotent, non-destructive reads, so the added value here is ordering ('newest first'), the 500-post cap with truncation signalling, and the flag for platform-removed posts — all genuinely behavioral and not derivable from annotations. The gap is that truncation is disclosed without explaining how to retrieve the remainder, and 'free' is asserted twice.

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?

Front-loaded with purpose, then the return payload, then downstream chaining — a sensible order. It loses a point for the long field run-on and the redundant 'Free to call. ... Cost: free.' duplication that occupies a whole trailing sentence without adding information.

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?

With no output schema, the description does the necessary work of enumerating the return payload, its ordering, and its size limit — enough for an agent to consume the result correctly. The one unresolved element is what to do when the response reports truncation, since no paging parameter exists in the schema.

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 coverage is 100% for the single projectId parameter, and the schema already states it comes from list_projects, so the description adds no syntax or format meaning. Baseline 3 applies since the schema carries the parameter semantics.

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 and resource ('Returns a single project by projectId with every saved post'), scoping it clearly apart from list_projects and get_post. The inline enumeration of returned fields makes the tool's output identity unambiguous before the agent opens any schema.

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 'single project by projectId' framing plus the pointer that a postId from this result feeds request_transcript, request_visual_analysis, or remix_post gives concrete when-to-use and chaining guidance. It stops short of an explicit exclusion ('for all projects use list_projects'), leaving that inference to the schema note.

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