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

Beyond the readOnly/idempotent annotations, it discloses data sources (members' marked-sent messages and emails Parse sent), the 30-day window, and a privacy constraint (another workspace is never named and nothing it wrote is shown). That's real behavioral context, though it doesn't cover latency or edge cases like missing tasks.

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 'use before sending' trigger and packs the return shape into one dense paragraph. It is information-rich but slightly run-on, with the verdict list embedded mid-sentence.

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?

The output schema exists, yet the description still usefully names the verdict values and canPitch so an agent can reason about results. Combined with the read-only annotation and full schema coverage, an agent has what it needs to call and interpret this tool.

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 description coverage is 100% and both parameters are documented there (id, brandSlug). The description adds no syntax or format detail beyond the schema, so the 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?

States a specific action (check whether this or another Parse workspace wrote to the task's page/recipient/site in the last 30 days) and enumerates the verdict outputs. An agent can distinguish it from siblings like parse_next_tasks or parse_mark_sent, which is uncommon for such a crowded toolset.

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 says 'Use before sending a page task's message' and gives a follow-up rule: when canPitch is false, tell the user and skip the task. It doesn't name an alternative sibling, but the triggering condition is clear.

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