search_by_title

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

With no annotations provided, the description carries the full burden. It states matching behavior but does not disclose what the return value looks like (single poem vs. list), whether results are sorted, or any limitations such as number of results. The 'exact or partial' hint is insufficient for an agent to predict behavior confidently.

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 two sentences, compact and front-loaded with the core purpose. It wastes no words, though it could add a bit more detail without becoming verbose.

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 simple search tool with one parameter and no output schema, the description is minimal. It fails to explain what the tool returns, whether it returns a collection, and any edge cases like no matches. The lack of annotations and output schema makes this description insufficient for confident usage.

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?

Schema description coverage is 100%, so the baseline is 3. The description essentially restates the schema field ('Poem title or partial title') without adding new semantics such as case sensitivity, matching precedence, or format requirements. No additional value beyond the schema.

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 and resource ('Find a poem by title') and specifies search matching behavior ('exact or partial title matches'). It does not name a specific sibling to differentiate from, but the title-based search is distinct enough among the listed tools; however, it could be more explicit about when to prefer it over search_combined.

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 use this tool vs. alternatives like search_by_author, search_by_lines, or search_combined. The description only implies that if you have a title, you can use this, but it never mentions exclusions or when not to use it.

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