mastodon_post

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

With no annotations, description discloses character limit (500), return format, and common errors (VALIDATION_ERROR, PLATFORM_ERROR). Adds behavioral context beyond basic post action, though could mention rate limits or idempotency.

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?

Three sentences; each conveys essential info (action, credentials, limits, return, errors). No redundancy or filler.

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?

Despite no output schema, return format is described. Errors, credentials, and behavior are covered. All parameters are explained in schema or description. Sufficient for an agent to invoke 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 coverage is 100% but description adds value by explaining mutual exclusivity of 'text' and 'thread', and that 'max_length' overrides default limit. Could clarify that thread creates replies referencing previous posts.

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?

Describes specific verb 'post' and resource 'Mastodon instance', with distinction between single status and threaded series. Clearly differentiates from sibling tools targeting other platforms like Bluesky or X.

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?

Mentions required credentials (instance_url, access_token) and scope, and notes that the tool is free. Implicitly distinguishes from other platform-specific tools via platform name, but no explicit when-not-to-use or alternative recommendations.

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