zernio_boost_post

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 states the tool is a paid action (budget), which is critical, but it does not disclose authorization requirements, whether the post's original content is altered, or any billing/cost implications. The basic behavioral trait of being a paid ad creation is clear, but lacks depth.

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?

A single, well-structured sentence that conveys the core purpose without extraneous details. It is efficient and front-loaded with the key action and objects.

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?

Given the absence of an output schema and the tool's financial nature (paid boost), the description is somewhat bare. It lacks information about return values, success/failure indicators, or how budget and duration interact. For a potentially costly operation, more behavioral context would be valuable.

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 input schema has 100% description coverage for all 5 parameters. The description adds no additional meaning beyond the schema; it only mentions 'budget and target audience' in passing. The baseline is 3 since the schema already documents parameters adequately.

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 the action ('boost an existing social media post as a paid ad') and key resources ('budget and target audience'). It distinguishes the tool from siblings like zernio_create_ad (which likely creates a new ad from scratch) and zernio_publish_post_now (which publishes without payment). The verb 'boost' is specific and appropriately scoped.

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 the tool is for promoting an existing post with paid spend, but it does not explicitly state when to use it versus alternatives like zernio_create_ad or zernio_publish_post_now. No when-not-to-use or prerequisite information is provided, leaving the agent to infer usage context from sibling names.

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