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

The description discloses important behavioral traits beyond the annotations: it creates a draft, requests an image, costs AI credits, refuses duplicates within 30 days unless force is set, and refuses competitors under a standing block. These details help an agent predict side effects and failure modes, especially since the annotations only signal non-read-only, non-idempotent, non-destructive behavior.

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 dense but every sentence earns its place: the action, the grounding rules, the refusal conditions, and the cost warning. It is front-loaded with the main purpose and avoids filler or repetition.

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 having no output schema, the description provides enough context for correct invocation: what the tool does, what inputs matter, key edge cases (duplicate and block), and the side-effect cost. An agent can confidently decide when to call it and what to expect afterward.

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 already documents slug and force well, covering 67% of parameters. The description reinforces the force behavior but adds little about workspaceId, which remains undocumented. This is adequate but not exceptional; the description does not go beyond the schema in a meaningful way for parameter understanding.

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 action ('Draft a LinkedIn post about one competitor from the demand ranking') and a clear deliverable ('draft content post with an image requested'). It also distinguishes this from generic post-creation tools by emphasizing grounding in demand data and exclusion of feature/pricing comparisons.

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 context is explicit: this tool is for drafting LinkedIn posts about competitors ranked by demand data. It adds practical usage constraints, such as the 30-day duplicate refusal and the force flag to override, which guides when to call it. It stops short of naming alternative sibling tools, but the use case is clearly scoped.

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