mdl_search_titles

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that pagination starts at 1 and that filters is a JSON object of upstream parameters, which is modest added context, but it says nothing about rate limits, result caps, or the meaning of 'upstream'.

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?

Three short clauses, front-loaded with the core purpose. It is efficient, though the phrasing ('upstream parameters') is slightly cryptic rather than wasteful.

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?

With five parameters at 0% schema coverage, no output schema, and a required query plus unexplained edge/synopsis fields, the description leaves significant gaps for a search tool whose pagination and filtering behavior an agent needs to invoke it correctly.

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 0%, so the description must carry the full parameter burden, yet it only clarifies 'page' (starts at 1) and 'filters' (a JSON object). The 'edge' and 'synopsis' parameters are entirely unexplained, and the required 'query' is only implied.

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+resource ('Search: titles'), which an agent can distinguish from siblings like mdl_search_people or mdl_titles_search_tags. However, it offers no explicit differentiation or scope statement versus those siblings.

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 use this tool versus alternatives such as mdl_titles_search_tags or mdl_search_top_dramas. The only directive ('Use filters for additional upstream search parameters') is about a parameter, not about tool selection.

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