mastodon_action

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

No annotations are provided, and the description does not disclose behavioral traits such as idempotency, side effects, or rate limits. It merely says 'Perform' without indicating which actions are read-only versus write operations. An agent cannot infer safety or cost implications from this description.

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 short (one sentence) but poorly structured. The list of actions is run together, making it harder to parse. It could be more effective with bullet points or clearer separation. However, it avoids unnecessary verbosity.

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 the tool's complexity (8 parameters, no schema descriptions, no output schema), the description is far from complete. It fails to explain how to use the parameters, what each action expects as input, or what the response looks like. The agent lacks critical context to invoke the tool 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 0%, so the description must compensate for parameter meanings. However, it only lists action names without explaining the role of 'status', 'id', 'q', 'acct', or other parameters. The agent cannot determine which parameters are needed for each action from the description alone.

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 tool performs Mastodon actions and lists nine specific action types. While it doesn't explicitly frame it as a router/dispatcher, the enumeration of actions provides adequate purpose clarity. However, it lacks a verb+resource structure that distinguishes it from sibling tools like bluesky_action.

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 is provided on when to use this tool versus alternatives. With many sibling tools (e.g., bluesky_action, slack_action), the description should indicate scenarios where this dispatcher is appropriate or mention that dedicated tools might be preferable for single actions. The description offers no such context.

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