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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds relevant behavioral context by stating that sharing 'changes no funding, claim, verification, settlement, or payment state' and by explaining how the original image remains attached when bounty_image_url is passed. No contradiction with annotations.

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 compact at three sentences, front-loads the main use case, and avoids generic filler. Each sentence adds meaningful guidance, though the parameter guidance is limited.

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?

The description covers when to use the tool, the no-side-effect guarantee, and the key image parameter. However, with 8 parameters and only 25% schema coverage, more context about how to populate required fields or how the share card relates to sibling tools would make it more complete. The presence of an output schema mitigates some of this gap.

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 only 25%, with only stage and bounty_image_url described in the schema. The description adds guidance for bounty_image_url but does little to explain the meaning or expected format of the other parameters, such as title, status, bounty_url, reward, and payment_state. Since coverage is low, the description needed to compensate more.

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 purpose: producing a factual social-ready caption and card intent after a bounty step. It clearly identifies the tool's resource (share bundle/card) and the user goal, though it does not explicitly differentiate it from sibling tools like prepare_bounty_post or prepare_bounty_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?

The description gives an explicit trigger: 'Use this when the person wants a factual social-ready caption and card intent after a bounty step.' It also clarifies that sharing is optional and has no state-changing effects. However, it does not mention when not to use it or name alternative tools for related intents.

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