mastodon_action

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

No annotations exist, and the description lacks any disclosure of behavioral traits (e.g., side effects, auth requirements, rate limits). It lists actions but does not explain their impact or safety profile.

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, which is concise but not well-structured. It lists sub-actions without any hierarchy or explanation, making it minimally informative.

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?

With no annotations, no output schema, and 0% schema coverage, the description is completely inadequate. It fails to provide enough context for an agent to correctly select and invoke the tool across its multiple actions.

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%, and the description adds no meaning to the 8 parameters. It does not explain when to use 'status', 'in_reply_to_id', 'id', 'q', 'acct', etc., leaving the agent without guidance.

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 lists supported sub-actions (mastodon_post, read_timeline, etc.) but the overall purpose is generic ('Perform a Mastodon action'). It does not distinguish itself from sibling tools like bluesky_action or other social media action tools.

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 provided on when to use this tool vs alternatives. No context on when-not to use it or which sub-action to choose in different scenarios.

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