list_system_searches

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the HTTP endpoint 'GET /api/system/searches', reinforcing the read-only nature, but adds little behavioral detail beyond what annotations already provide.

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 very concise and well-structured: a one-line summary, the endpoint, and an Args section. No filler or unnecessary repetition, though it is somewhat minimal.

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, one-parameter, read-only tool with an output schema and comprehensive annotations, the description is largely sufficient. The main gap is lack of context about when this search tool is the appropriate choice relative to other listing tools.

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 carries the burden of explaining the 'query' parameter. It does so usefully by specifying it is a 'Series or movie name to search for', adding semantic meaning not present in the schema itself.

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 the action ('List') and identifies the resource via the endpoint 'GET /api/system/searches'. The query parameter is clarified as a 'Series or movie name to search for', making the core purpose understandable. However, it does not explicitly distinguish this tool from siblings like list_movies or list_series.

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?

Usage is only implied through the parameter description: 'Series or movie name to search for'. There is no explicit guidance about when to prefer this tool over alternative list/search tools, nor any mention of 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.