search_titles

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

With annotations present (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), the description adds no behavioral context. It does not explain what the search does with the 'body' parameter, how results are ordered, or what visibility scope applies, so the agent has no idea what to expect beyond the annotations.

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 extremely brief—two words—but this is under-specification rather than effective conciseness. It lacks a complete sentence and fails to structure any useful information for a tool with a complex body parameter and multiple options.

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?

Given the tool's complexity (required array body, pagination, ordering, and sibling tools for listing/retrieving), the description is grossly incomplete. It does not explain what 'search' means here, how the body shapes the query, or how results are returned, making it inadequate for selection and invocation.

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 has 100% description coverage for all four parameters (body, limit, offset, order_by), so the description does not need to repeat parameter details. The description itself adds no parameter-level meaning beyond the schema, matching the baseline of 3.

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 clearly states the verb 'Search' and resource 'titles', indicating a search operation over title entities. However, it does not differentiate from sibling tools like 'list_titles' or 'get_title', so it lacks scope or distinguishing details.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'list_titles' or 'get_title'. No context, prerequisites, or exclusions are mentioned, leaving the agent without direction on selection.

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