x_get_post

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

The readOnlyHint annotation already declares this as a safe read, so the description's remaining burden is lower. It adds little beyond the annotation: no mention of auth requirements, deleted/protected post behavior, or rate limits. A 3 reflects that annotations carry the safety profile while the description adds almost nothing.

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?

A single, front-loaded sentence with zero waste. Appropriate for a simple lookup tool.

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 basic read-by-ID tool with annotations covering safety, this is minimally adequate. Missing are edge-case behavior, format of the ID, and sibling differentiation, leaving some gaps for an agent choosing among post-related tools.

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?

There is only one parameter, so the baseline is 4. Schema coverage is 0% and the description only restates 'by ID', but with a single obvious parameter the description is adequate.

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 states a specific verb and resource: retrieving a single X post by ID. It is clear on its own, but it offers no distinction from siblings like x_search_posts or x_get_user_posts, which also return post data.

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?

There is no guidance on when to use this tool versus x_search_posts or x_get_user_posts. The word 'single' implies an exact-ID lookup, but this is not explicit and no alternatives or exclusions are named.

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