tvh_list_classes

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only that results can be narrowed by name/caption; it says nothing about result size, ordering, or what a 'class' represents, which for a discovery tool would have been genuinely additive.

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?

One short sentence with the resource and the filter option front-loaded; no filler, nothing redundant with the schema.

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 values need no explanation, and the tool is simple (zero required params). Still, the agent is left unsure what a Tvheadend 'class' is and when this beats direct schema/API read tools, which is a meaningful gap for the exploration phase of a workflow.

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% and the single parameter is named only 'contains', so the description has to carry the meaning — it does confirm the filter targets name/caption. However it never states that matching is substring-based or whether it is case-sensitive, leaving the parameter's exact semantics unresolved.

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 concrete verb ('Discover') and a concrete resource ('Tvheadend class names'), plus the optional filter. It is distinguishable from the create_/list_channels-style siblings, though it never clarifies how 'class names' relates to the neighboring introspection tools tvh_get_schema and tvh_api_read.

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 phrase 'optionally filtering name/caption' implies a discovery-then-filter workflow, but there is no explicit when-to-use guidance or pointer to alternatives such as tvh_get_schema or tvh_get_field_options for schema exploration.

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