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

With no annotations, the description carries the full burden. It discloses the auth requirement (editor key) and that each card is a proposed change surfaced through an attached widget, which implies a read operation, but it never states read-only behavior, pagination, or what happens if the key is missing.

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?

Three sentences, front-loaded with what is returned, followed by domain context and the auth requirement. The 'too big to make on its own' phrasing is slightly narrative but earns its place by explaining what a card is.

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?

No output schema exists, so the description must characterize the return value, and it does ('Returns the cards'). Combined with the auth note and the widget behavior, it is nearly complete for a one-parameter retrieval tool, though it omits ordering or volume expectations.

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 the single parameter is already documented as an optional fallback when the connector sends a bearer header. The description's 'Requires the editor key' adds a mild auth note but does not extend the schema's meaning, so baseline 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 names a specific resource (the site editor's pitch cards awaiting Mike's decision) and the verb-equivalent action (returns the cards), so an agent knows it retrieves pending proposed changes. It does not explicitly name the sibling editor_decide as the action counterpart, leaving differentiation partly to inference.

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: fetch the pending cards, then use the attached widget to Approve / Hold / Kill each one. There is no explicit statement of when to call this versus editor_decide, nor any exclusion or ordering guidance, so the agent must infer the workflow.

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