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

Goes well past the annotations (readOnly=false, idempotent=true, destructive=false, openWorld=false) by disclosing the auth requirement and exact scope (blog.write), the anonymous-call failure mode, the no-rewrite/no-fact-check contract placing authoring burden on the caller, the downstream side effects (diagram rendering, media storage, preview email with editor/approve links), and the tasks-extension completion signal. No statement conflicts with the annotations.

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?

Front-loads the highest-risk constraint (sign-in and scope) and keeps to one paragraph with no filler, but several clauses are densely nested in parentheses, which slows scanning for the core submit action.

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 no output schema, the description still closes the loop by naming the return value (the idea id) and the asynchronous completion path for tasks-extension clients. Combined with the auth, side-effect and no-publication disclosures, an agent has everything needed to call this correctly.

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 67%, and the description compensates by specifying that markdown must contain frontmatter with at least title and description, and that the draft is stored exactly as sent. It does not describe how images entries map into the post beyond what the schema's alt/data/name descriptions already say, so it adds real but partial meaning.

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 and resource — files a post into techfabric.com's blog pipeline under the signed-in engineer's byline — and the mass-noun scope (draft, not published). It is clearly distinguishable from check_draft (validates) and update_draft (edits existing), so an agent can route without opening schemas.

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?

Explicitly routes the agent: 'Run check_draft first; what the draft still lacks comes back as findings,' and constrains behaviour with 'Never publishes.' It does not say when to prefer update_draft over a resubmission, so the sibling coverage is strong but not complete.

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