kodi_settings

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results carry current and default values, which is genuine behavioral context, but says nothing about pagination behavior, query semantics, or result size limits.

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?

A single front-loaded sentence with no filler; the purpose comes first and the rationale trails. It is slightly terse for a tool with three undocumented parameters, but nothing is wasted.

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?

An output schema exists, so return-value explanation is not required, and the read-only annotations cover safety. Still, for a 3-parameter search tool at 0% schema coverage, the description leaves query and paging semantics under-specified.

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 load. 'Search/page' does map meaningfully onto the three params (query = search term, limit/start = paging), giving partial compensation, but it never clarifies query matching syntax, limit bounds, or start offset semantics.

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?

States a specific verb (search/page) and resource (Kodi's expert settings) plus what is returned (current/default values). The phrase 'expert settings' implicitly distinguishes it from the sibling kodi_addon_settings / kodi_set_setting, though it never names an alternative explicitly.

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 clause 'avoiding a whole-schema dump' implies this is the lightweight, filtered alternative to reading the full schema, which is useful implied usage guidance. However, no explicit when-to-use condition or named alternative tool is given, so the agent must infer the routing.

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