List public Hermai schemas

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's 'Read-only' adds no new behavioral information. The description does not disclose additional traits such as pagination behavior, authentication requirements, or rate limits, but it does not contradict the annotations.

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 a single, front-loaded sentence that immediately conveys the tool's purpose. It has zero wasted words and earns its place by being directly actionable.

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?

Given the absence of an output schema, the description does not clarify what information is returned (e.g., schema names, metadata). It adequately covers the tool's input behavior but leaves the output structure implicit, which could cause an agent to misunderstand the result format.

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 coverage is 100% with descriptions for all five parameters, so the baseline is 3. The description only mentions 'optional filters' generically, adding no specific semantic detail beyond what the schema provides (e.g., it does not explain valid values for 'sort' like 'trending' or 'recently_verified').

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 clearly specifies the action ('List'), the resource ('public schemas'), and the scope ('in the Hermai registry with optional filters'). It effectively distinguishes itself from sibling tools like lookup_schema (which likely targets individual schemas) and submit_schema_request (a write operation).

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 description provides no guidance on when to use this tool versus alternatives like lookup_schema or submit_schema_request. It mentions 'optional filters' but does not explain the selection criteria or trade-offs between this and sibling tools.

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