List components

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

The readOnlyHint annotation already conveys the safe read-only nature, and the description aligns with that. It adds the notion of filtering but doesn't disclose return structure, pagination, or default behavior with no filters. No contradiction.

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 one sentence and front-loaded with 'component catalogue', making it concise. However, it is a noun phrase rather than an explicit verb phrase, which slightly reduces actionability.

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?

For a simple list tool with two optional enum parameters, the description is adequate but leaves out what the returned catalogue entries look like and what happens when no filters are applied. Without an output schema, a bit more return context would be helpful.

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?

Both parameters are fully described in the schema with enums and descriptions, so the description's mention of 'filtered by category or status' adds no new meaning. Schema coverage is 100%, so the schema carries the semantic weight.

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 identifies the tool as 'the component catalogue', implying a list of components with optional filters. It is clear enough, but it relies on the title for the verb and doesn't explicitly differentiate from siblings like get_component or search.

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 such as get_component or search. The optional filters hint at usage context, but there is no explicit when-to-use or when-not-to-use guidance.

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