Post a press release with credits

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

The description indicates a mutation ('posts') and mentions that it returns an error for free accounts, making the side effects and failure conditions transparent. It does not claim to be read-only or hide the write nature of the operation.

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 two sentences, directly communicates the core action and constraints, and contains no unnecessary words or repetition. It is well-structured and efficient.

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?

It provides sufficient context for an agent to decide when to call the tool, including the membership requirement, the error condition for free accounts, and the cost in credits. It also clarifies the action and target, making it complete for the given scope.

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?

The schema already provides descriptions for both parameters (press_release_id and days) with 100% coverage, so the description text adds limited new meaning about the parameters themselves. It does provide context about credits and duration, but this is more about usage than parameter semantics. Baseline of 3 is appropriate.

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 that the tool posts an existing press release to the home-page widget, specifies the required credits and duration, and mentions the membership requirement. The action, object, and destination are unambiguous.

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?

It explicitly states that a paid membership (Bronze/Silver/Gold) is required and that free accounts will receive an error, providing clear guidance on when to use and when not to use the tool. It also mentions the credit cost and duration, which inform usage decisions.

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