draft_post

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

No annotations provided, so the description must fully disclose behavior. It only states 'generate a template' without revealing if this is a read-only operation, whether it calls external APIs, has side effects, or requires authentication. Agent cannot assess safety or constraints.

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?

Single sentence is concise, but it sacrifices informativeness. Key behavioral and parameter details are omitted; the tool definition would benefit from a few more sentences to improve clarity without being verbose.

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?

With 7 parameters, low schema coverage, no output schema, and no annotations, the description is insufficient for correct invocation. Agent lacks understanding of expected output format, parameter interactions, and usage context.

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 low (43%). Description only mentions 'topic and tone', which are already described in the schema. It does not add meaning for key_points, hashtag_count, target_audience, or cta, failing to compensate for missing schema descriptions.

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?

Description clearly states it generates a LinkedIn post template based on topic and tone. Verb and resource are clear, and the tool is distinguished from siblings (analyze, create, format, generate_hashtags) by implying a draft/pre-creation step, though explicit differentiation is missing.

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?

No guidance on when to use this tool versus siblings like create_post or analyze_post. The description does not mention prerequisites, outcomes, or alternative scenarios, leaving the agent to infer usage context.

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