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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real value by naming the auth requirement (Microsoft sign-in, blog.write scope) and by stating 'No model is called and nothing is posted.' It also enumerates what the response contains, which is useful orientation even though an output schema exists. Missing only things like rate limits or behavior for an unpublished/unknown slug.

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?

Every sentence carries information and the prerequisite (sign-in scope) is front-loaded, followed by what is returned and the workflow. The middle enumeration of kit contents is a comma-spliced list of fragments that reads a little breathlessly, but nothing is redundant.

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 read-only, single-parameter tool with annotations and an output schema, the description covers the essentials: access prerequisite, contents, absence of side effects, and next steps. It would be fully complete with a note on what happens when the supplied post is not published.

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?

A single parameter with 100% schema description coverage, so the schema already explains the URL/slug format. The description adds one genuinely useful clarification — 'any post on the site', not just the engineer's own — but provides no error semantics for unpublished posts or invalid slugs. That is the expected baseline-3 level when the schema does the heavy lifting.

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 concrete verb and resource: reads a drafting kit (key points, first-hand sentences, campaign link, voice notes, social rules, LinkedIn lengths) for a published techfabric.com post. The LinkedIn scope implicitly separates it from reddit_post_kit, and it explicitly hands off to lint_social. The wording 'A read: what your agent needs to draft...' is a bit indirect as an opening statement of purpose, keeping it just short of a 5.

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?

Gives an explicit workflow: draft the post from this kit, validate with lint_social, then show the engineer the text so they post it themselves. That is clear when-to-use guidance and names the correct downstream sibling. It lacks an explicit exclusion (e.g., 'for Reddit posts use reddit_post_kit'), so it stops at 4.

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