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

Annotations already declare idempotentHint=true and destructiveHint=true, and the description adds a useful behavioral note ('Does not mark ready') plus the two-layer evaluation model. But it never explains the destructive/'does not mark ready' tension or what state a run touches, which matters for a tool flagged destructive.

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?

Purpose and the 'Does not mark ready' caveat are front-loaded, which is good, but the long embedded enumeration of every editorial rule is dense and largely duplicates what get_skill is said to contain, costing readability.

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 usefully hints at the return shape ('one list of findings') and covers the two rule layers. Combined with the pointer to get_skill and the no-output caveat, an agent has enough to invoke it, though parameter semantics remain thin.

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 only 50%: workspaceId is documented in the schema while id has no description. The description says 'a post' but never maps that to the required id parameter or explains scoping/fallback behavior, so it fails to compensate for the undocumented required parameter.

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 ('Check a post against the seodraft rules') and immediately scopes the work into two named layers (package rules, editorial rules), so an agent can tell it apart from siblings like approve_post or get_post. The closing 'Does not mark ready' sharpens the boundary further.

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?

It names the companion tool to read ('Read get_skill for what each rule wants') and implies the contrast with approve_post through 'Does not mark ready'. However it never states the trigger conditions explicitly (e.g., run this before delivery/approval), so usage context is clear but not fully specified.

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