list_editorial_projects

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'List' and mentions the returned 'workflow status', which is useful context. However, it does not disclose pagination, ordering, scope (all projects vs. scoped), or whether any side effects exist. For a simple no-parameter list, this is minimally adequate.

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?

The description is a single, front-loaded sentence with no filler. It efficiently communicates both the resource and the key output attribute without wasting words.

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 description covers the core purpose but leaves several details unspecified: it does not state whether all projects are returned, whether results are ordered or paginated, or what the exact response structure looks like. Given there is no output schema or annotations, more context would be valuable, but for a trivial no-parameter list tool the description is acceptable.

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 input schema is empty ({}), meaning there are no parameters to document. The baseline for 0 parameters is 4, and the description includes no misleading or contradictory parameter information.

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 uses a specific verb ('List') and clearly identifies the resource ('editorial projects') and an attribute of interest ('workflow status'). This clearly distinguishes the tool from the singular get_editorial_project, though it does not explicitly name sibling alternatives.

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?

No guidance is given about when to use this tool versus the sibling tools (e.g., get_editorial_project or create_editorial_project). There is no mention of prerequisites, exclusions, or scenarios where a different tool would be more appropriate.

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