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

With no annotations, the description carries the full burden, but it only states the data returned. It does not disclose whether the operation is read-only, requires auth, paginates, filters, or what happens for empty results.

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 10-word phrase with no filler. Everything present ('Published', 'metadata', 'citation URLs') adds information beyond the title.

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 parameterless list operation, the description is minimally adequate: it names the resource and the kind of return data. However, with no output schema and no annotations, it leaves return-shape details and usage-vs-sibling decisions unspecified.

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 has zero parameters and the input schema documents this completely, so there is no parameter burden for the description to carry. The baseline of 4 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 title and name supply the verb ('List') and resource ('case studies'), and the description adds the scope 'Published' plus what is returned (metadata and citation URLs). It is clear enough to distinguish from the singular get_case_study and list_writing, but it does not explicitly call out any sibling or contrast.

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 on when to call this tool instead of get_case_study, search_writing, or list_writing. The only clue is the plural 'list' naming, which is implied rather than stated.

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