Pipepost

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

With no annotations provided, the description carries full burden. It discloses authentication requirements and cost implications ('FREE — no credit cost'), but doesn't mention rate limits, error handling, whether posts are editable/deletable, or what the response looks like. For a write operation with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely efficient - three sentences with zero waste. It's front-loaded with the core purpose, followed by prerequisites and cost information. Every sentence earns its place by providing essential context.

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 this is a write operation with no annotations and no output schema, the description should do more to explain behavioral aspects. While it covers purpose, prerequisites, and cost well, it lacks information about what happens after posting, error conditions, or platform-specific constraints that would help an agent use it 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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Post directly'), target resource ('any Mastodon instance'), and format options ('single post or a threaded series'). It distinguishes from sibling tools like 'bluesky_post' by specifying the Mastodon platform and thread capability.

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 clear context about prerequisites ('Requires instance_url + access_token via setup') and indicates when to use ('FREE — no credit cost'). However, it doesn't explicitly state when NOT to use this tool versus alternatives like 'bluesky_post' or 'x_post' for other platforms.

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