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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description is free to add the genuinely useful trait: missing inputs are left as [brackets] and nothing is invented. That is real behavioral context an agent could not get from structured fields, though it says nothing about how many hooks come back.

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?

Two short sentences, zero waste. The output shape is front-loaded and the placeholder rule follows immediately as the operative constraint.

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?

No output schema exists, and the description does cover the return shape at a high level ('opening-line templates') plus the placeholder convention. It stops short of saying how many hooks are produced or their format/length, which is the one thing an agent would still want to know.

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 100%, so baseline is 3. The description goes slightly beyond the schema by explaining the consequence of leaving optional fields empty — the output keeps bracketed placeholders — which tells the agent that audience and result may be omitted deliberately rather than being required for a good result.

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?

States a specific verb+resource: it produces opening-line templates (hooks) for a LinkedIn post, parameterized by topic, audience and result. This implicitly separates it from generate_linkedin_headlines, but it never names that sibling explicitly, so differentiation is left to inference.

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?

Usage is only implied: the agent can infer this belongs at the start of drafting a LinkedIn post. There is no statement of when to prefer it over generate_linkedin_headlines or format_linkedin_post, and no prerequisites or exclusions are given.

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