list_content_views

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

No annotations provided, so description must cover behavior. It discloses default field set and pagination hint, but omits details like sorting, error behavior, or idempotency. Moderate transparency, but could specify that it's a read-only operation.

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?

Description is well-structured with separate sections for purpose, context optimization, and field filtering. Front-loaded with primary action. Slightly wordy but efficient with no redundancy.

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?

Covers primary functionality and key parameters. Missing details on output structure (no output schema) and error handling, but for a simple list tool with only 2 parameters, the description is fairly complete.

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 0% schema description coverage, description adds meaning: explains per_page usage and include_fields options ('all' or comma-separated). Could be improved by listing example field names, but sufficiently compensates for schema gaps.

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 states 'List all content views in Foreman/Katello with field filtering,' specifying verb, resource, and scope. It distinguishes from sibling 'get_content_view' which retrieves a single CV.

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?

Provides explicit context optimization (use per_page=5-10) and field filtering guidance (include_fields='all' or comma-separated). Implicitly suggests using get_content_view for a specific CV, but lacks explicit 'when not to use' statements.

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