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

Annotations already declare this as a safe read, and the description adds substantial behavioral detail: returned fields, status values, last_error, queue counts, scheduling horizon, and source/publish semantics. No contradictions with annotations.

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-loaded with the purpose, then structured into source_type, kind, return values, and sibling guidance. It is information-dense and long for a list tool, but most sentences earn their place by compensating for the missing output schema.

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?

Given one parameter, no output schema, and a domain-specific resource, the description is complete. It explains the workflow model, returned fields, status meanings, queue data, and where to look for reposted items.

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?

The schema fully documents workspace_id and points to list_workspaces, so the high schema coverage sets a baseline of 3. The description does not add meaning beyond the schema for the sole 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 ('Lists a workspace's Repurposing workflows') and distinguishes it from list_repurposing_workflow_posts. The domain explanation makes the resource unambiguous without needing the schema.

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 points to list_repurposing_workflow_posts for reposted or scheduled items, which is a clear alternative. It does not explicitly state when not to use this tool versus create/update/delete siblings, but the listing purpose is clear.

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