seerr_list_settings_metadatas

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

The description adds nothing beyond the readOnlyHint annotation. It does not mention what the response contains, whether any cached data is used, or any operational details. Since the annotation already indicates a safe read operation, the description's lack of extra context provides marginal value at best.

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 short ('Get Metadata settings'), which is efficient but also under-specified. It is not a full sentence and lacks any contextual structure. While there is no fluff, the brevity borders on under-specification rather than focused conciseness.

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?

Even though the tool has no parameters, an output schema, and a read-only annotation, the description fails to explain what 'metadata settings' refers to in this system. An agent might confuse it with other settings categories. A brief clarification (e.g., 'metadata providers such as TMDB and TVDB') would greatly improve completeness.

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 and the schema is an empty object, so schema coverage is 100%. Per the baseline for 0 params, the description does not need to explain parameters. It correctly omits any parameter details.

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 uses a clear verb+resource structure: 'Get Metadata settings'. It identifies the action (get) and the resource (metadata settings), distinguishing it from sibling tools that create or update metadata settings. However, it does not define what 'metadata settings' actually includes, making it less clear than if it listed specific fields or scope.

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 versus alternatives like seerr_update_settings_metadatas or other list settings tools. It does not state typical use cases, prerequisites, or exclusions. The bare phrase leaves the agent to infer that it is for retrieving current metadata settings.

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