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

Beyond readOnlyHint/idempotentHint it discloses the auth requirement and scope, and explicitly negates side effects: 'No model is called and nothing is posted, voted or commented.' It also previews the output contents (rules, frame, disclosure line, checklist, posting steps), which is exactly the behavioral context an agent needs before calling.

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?

Length is reasonable for a 5-parameter tool, and the auth prerequisite is front-loaded. But the prose is telegraphic and run-on — fragments like 'A read:' and 'Send draft to check it:' pack the lint-and-rewrite loop into a sentence that reads as a separate capability, costing clarity.

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 an output schema present, return values needn't be explained, and the description covers auth, inputs, style constraints and the rewrite loop. What it leaves ambiguous is whether one call produces both the drafting kit and lint, and how it differs from check_draft/lint_draft.

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% and every parameter is documented inline, so the baseline is 3. The description adds only ambient meaning — that output is tailored to the target subreddit's rules and that the post/notes inputs are the raw material — without new syntax or format guidance beyond the schema.

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?

It names a concrete resource and scope: a read that returns everything needed to draft a Reddit post or thread answer from a techfabric.com post or notes. The second half adds a second apparent capability (send a draft and get lint back), which slightly muddies what the tool actually returns, and it never names the sibling it supersedes for non-Reddit channels (social_post_kit).

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?

'Requires a TechFabric engineer's Microsoft sign-in (scope blog.write)' plus 'from a published techfabric.com post or your own notes' gives a clear trigger condition and precondition. It also states the iteration loop ('send it again after each rewrite until lint.ready is true'). No exclusion or explicit alternative is given, so it stops short of a 5.

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