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

Annotations only mark non-read-only/non-idempotent/non-destructive, so the description adds real value by clarifying that the post is created as a draft, returns the new post ID, and infers postType from media. This goes beyond the structured hints; it could additionally disclose scheduling side effects, but those are covered by parameter descriptions.

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 and front-loaded with the primary action and return value, then moves to inference rules and tags. Every sentence carries information that helps an agent call the tool correctly, with no 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?

For a 9-parameter create operation with no output schema, the description covers the key behavioral nuances, return value, and retrieval route. The remaining gaps (specific meaning of body/authorAccountId, scheduling workflow) are minor because the parameter names and schema descriptions make them inferable.

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 coverage is low (33%), so the description must compensate. It does add useful semantics for postType (auto-inference rules from media) and tags (system vs freeform tags), but it leaves required parameters like body and authorAccountId unexplained and repeats little beyond the schema for the other parameters.

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 first sentence names a specific verb ('creates'), resource ('draft content post'), and platform ('LinkedIn account'), and the description explicitly differentiates from retrieval via campaignstack_get_content_post. This is enough for an agent to know exactly what operation this tool performs.

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 states the core use case and directs the agent to campaignstack_get_content_post for retrieving the full post, but it does not give exclusion criteria against close siblings such as schedule_content_post, update_content_post, or submit_content_for_approval. Some usage context is implied by 'draft' and the scheduling parameters, but the when-not guidance is left to inference.

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