list_titles

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

No annotations are provided, so the description bears full responsibility. It only says 'list all poem titles', implying a read-only operation, but does not disclose whether results are paginated, limited, or sorted, nor what the return format is (e.g., array of strings). For a potentially large dataset, this is a notable gap for a tool with no output schema.

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?

A single sentence, perfectly concise and free of any filler. It communicates the purpose with minimal wording and does not include redundant details.

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 zero-parameter list operation, the description is adequate but not complete. It lacks any mention of output structure, potential large result sets, or whether the list is alphabetically ordered. These details would help an agent anticipate the response, but the core functionality is clear.

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, so the schema is already comprehensive. The description adds no parameter information, but nothing is needed. Baseline 4 applies since there are no parameters to elaborate on.

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 states a clear verb 'list' and a specific resource 'all poem titles in PoetryDB'. It is unambiguous and distinct from siblings like search_by_title (which filters) or list_authors (which lists authors). No further clarification needed.

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?

There is no guidance on when to choose this tool over siblings. It does not mention that it returns the entire set of titles, contrast with search_by_title for filtered queries, or note any pagination or size concerns. An agent must infer usage from the name alone.

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