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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real context beyond that: the return set includes every publication with your role, each publication enforces its own acceptance rules, and a Cotlet API key with app access is required. It omits pagination/ordering behavior, which keeps it from a 5.

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 statement and organized into short, purposeful sentences. There is minor redundancy between the first and second sentences, both of which restate 'with your role', which prevents a 5.

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?

For a no-parameter list tool with an empty schema and no output schema, the description covers what is returned (all publications, with role), why to call it, the downstream handoff, the publication-specific acceptance rules, and the auth prerequisite. Nothing an agent needs to invoke it correctly is missing.

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 tool takes zero parameters, so the baseline is 4 and there is no schema semantics to compensate for. The description's mention of publication_id is about downstream use with submit_to_publication, not an input 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?

Specific verb (list) + resource (publications) with a scoping qualifier: 'Publications you own, edit or write for, with your role.' This distinguishes it from sibling lists like list_stories by both the resource and the membership/role scope, and it names submit_to_publication as the downstream consumer.

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?

It gives a clear reason to call it (to obtain publication_id for submit_to_publication), which contextualizes usage. It stops short of explicit when-not guidance or naming alternatives such as list_stories, but the intended workflow is unambiguous.

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