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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, yet the description still adds substantive behavior: the exact return contents (reviewer notes, requester, timestamps) and the non-obvious state transition where a rejected post reverts to a draft. No output schema exists, so this return-shape disclosure is genuinely load-bearing.

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 tight sentences with zero filler. The state enumeration is front-loaded, and the follow-up workflow note is appended only after the core answer, which is the right ordering.

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 no output schema, the description covers what comes back and the lifecycle semantics. The only unaddressed case is what is returned when no approval request has ever been made for the post, a minor gap.

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?

There is a single required parameter, post_id, and schema description coverage is 100%, so the schema already carries the full burden. The description adds no syntax, format, or sourcing detail for post_id, which is the expected baseline when the schema is complete.

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?

The description names the resource (a post's approval) and enumerates the three states it reports (awaiting approval, approved, rejected), plus the ancillary data returned. That is far more specific than the title alone. It does not explicitly distinguish itself from the nearby sibling sprkly_get_post_status, which is the one ambiguity an agent could hit.

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 implied rather than stated: you call this to check approval state, and the second sentence gives a post-rejection workflow that points toward sprkly_request_post_approval. There is no explicit 'use this instead of X' or when-not-to-call guidance, and no statement of the prerequisite that an approval request must already exist.

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