list_claims

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

No annotations are provided, so the description carries the full burden. "List" implies a read, but it says nothing about volume, pagination, ordering, or what happens when the supplied feature does not exist (empty result vs error). For an unannotated tool this is a substantial disclosure gap.

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, front-loaded with the verb and resource, with zero filler. Brevity is appropriate, though it is terse to the point of omitting behavior rather than being padded.

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 shape needn't be described, but with no annotations, an undocumented filter parameter, and no statement of scoping or failure behavior, the definition is too thin for an agent to call it confidently.

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?

With a single parameter at 0% schema description coverage, the description must compensate; it does state that feature is optional and acts as a filter, which is the main semantic. It stops short of saying whether the value is a feature name/ID or how unknown or non-matching features are handled.

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 verb+resource pair ("List claims") is specific, and the optional feature scope is stated, but the domain term "claim" is never explained and nothing distinguishes this from siblings like list_rules or list_feature_unknowns. An agent can guess it enumerates claim objects but not what a claim is in this system.

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?

"optionally for one feature" hints at a filtering use case but gives no when-to-use/when-not guidance and never names an alternative (e.g., when to inspect claims via list_rules or a spec tool instead). The agent must infer selection criteria entirely.

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