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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait (does not spend posting quota), which adds useful context. However, it doesn't mention other behaviors like validation, authentication, or failure semantics, leaving some 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 one short, front-loaded sentence: 'Save a draft for later without spending posting quota.' Every word earns its place, with no redundancy or unnecessary detail.

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 two-parameter tool without an output schema, the description captures the core purpose and a key behavioral constraint. It lacks context about what happens after saving (e.g., where drafts go, how to publish later) and doesn't describe return values, but it's minimally complete for basic use.

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 50%: platforms has an example, content does not. The description doesn't explain parameters beyond the tool's purpose. Content is self-explanatory, and platforms is documented, so the description adds minimal value but doesn't need to compensate heavily.

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 states a specific verb ('Save') and resource ('a draft'), with a clear purpose ('for later') and a key differentiator ('without spending posting quota'). This distinguishes it from sibling tools like create_post, which presumably posts immediately.

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 implies when to use this tool: when you want to save something for later rather than publish immediately, avoiding posting quota. It doesn't explicitly name alternatives or exclusions, but the context is clear given sibling tools.

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