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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description adds value on state semantics instead: it explains that rejection demotes the post back to draft and must be re-requested, which is not derivable from any structured field. It does not say what status is returned if approval was never requested, nor whether notes can be absent, but the core behavioral nuance is disclosed.

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 sentences, zero waste: the return contents lead, and the consequence of rejection follows as actionable guidance. Every clause carries information and there is no restating of the title or the parameter.

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 correctly compensates by enumerating the substantive return fields (decision, reviewer notes, requester, timestamps). For a one-parameter read tool this is close to sufficient; only the never-requested / no-reviewer edge case is left unstated.

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 post_id and the schema already documents it at 100% coverage ('The scheduled post id.'). The description adds no format, sourcing, or lookup guidance for the id, so the schema does all the work and the baseline of 3 applies.

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 opens with a specific resource and the exact set of values it reports (awaiting approval / approved / rejected) plus the payload (reviewer notes, requester, timestamps). It is clearly distinct from write-side siblings like sprkly_request_post_approval, but it never explicitly distinguishes itself from the near-collider sprkly_get_post_status, leaving an agent to infer the split between general post status and approval status.

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 context is conveyed through the follow-up sentence: a rejected post becomes a draft, so the agent should fix it and call sprkly_request_post_approval again. That is real workflow guidance naming a specific next tool. What is missing is any statement of when to reach for this versus sprkly_get_post_status, and no exclusion or precondition is given.

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