get_post

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

The description only says 'Get', implying a read-only operation, but no annotations are provided. It does not disclose what happens if the post_id doesn't exist, authentication requirements (despite having cookies/account parameters), or any side effects. Minimal behavioral detail.

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 a single sentence of 8 words, directly stating the tool's function. It is front-loaded with the verb and resource, making it easy to scan. Every word is essential.

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 no annotations, no output schema, and only moderate schema coverage, the description lacks information about return format, error handling, authentication prerequisites, and parameter usage nuances. The agent would need additional context to use the tool safely and correctly.

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 input schema provides descriptions for account and cookies but not for post_id. The description adds that post_id identifies the post, but does not explain the role of account or cookies in authentication. With 67% schema coverage, the description partially compensates for the missing post_id description but falls short.

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 'Get a Grok media post by post_id', specifying the verb (Get), resource (Grok media post), and the key parameter (post_id). This distinguishes it from sibling tools like list_posts (listing) and create_media_post (creation) without ambiguity.

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 implies usage when the user has a post_id and wants the corresponding post object, but it does not explicitly state when to use this tool versus alternatives like list_posts or get_post_folders. No when-not-to-use guidance is provided.

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