list_domains

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

With no annotations, the description only adds a note about typical domain count and context safety, but fails to disclose pagination behavior (implied by per_page parameter), authentication needs, or return format.

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 very brief with no wasted words, though the context optimization note seems meta and could be integrated more elegantly.

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 simple tool (list with pagination, no output schema), the description omits what the returned data looks like, requiring the agent to assume common domain attributes. The size hint is helpful but not 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?

Schema description coverage is 0%, yet the description provides no explanation of the only parameter (per_page), leaving the agent to infer its meaning solely from the schema name and default.

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 'List all domains in Foreman' uses a specific verb and resource, clearly distinguishing it from sibling tools like list_architectures or get_domain.

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 on when to use this tool versus alternatives like get_domain or other list tools. The context optimization note is about behavior, not usage.

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