threads_get_post

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

No annotations provided, so description must carry the burden of behavioral disclosure. The description only says 'get details', which implies read-only, but does not explicitly state that it is safe, what authentication is needed, or any rate limits. No mention of errors or side effects.

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 sentence that is concise and front-loaded. No unnecessary words. Perfect density for the given purpose.

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 retrieval tool with no output schema and two simple parameters, the description is minimally adequate. However, it lacks any mention of returned data structure, field options, or error conditions. Given no annotations, more context would be helpful.

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 documentation coverage is 100% (both parameters described in schema). The description adds no extra meaning beyond the schema; it repeats 'Threads post ID' and 'Comma-separated fields' exactly as in the schema. Baseline 3 is appropriate as description adds no value.

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 details of a specific Threads post' which is a specific verb and resource. It distinguishes from list tools like 'threads_get_posts' but does not explicitly differentiate from other single-item retrieval tools among siblings.

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?

No guidance on when to use this tool versus alternatives such as 'threads_get_posts' for listing or 'ig_get_media' for Instagram posts. No context on prerequisites or intended use cases.

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