mautic_list_companies

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds only the raw HTTP endpoint (GET /api/companies), which contributes nothing an agent can act on; it says nothing about result volume, pagination behavior, MAUTIC_MAX_LIMIT interaction, or what a listing returns.

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?

Two short fragments with no wasted words and the purpose front-loaded, so it is efficient. However, the terseness crosses into under-specification rather than disciplined brevity, since the second sentence (the endpoint path) occupies space without adding actionable meaning.

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?

With six optional parameters, half of them undocumented, and no output schema, the description should carry much more weight than two fragments. An agent lacks enough information to call this correctly with ordering, minimal mode, or search syntax.

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 only 50%, with 'minimal', 'orderBy', and 'orderByDir' entirely undocumented in the schema, and the description supplies zero parameter information to compensate. An agent cannot tell from this definition what 'minimal' toggles or what fields 'orderBy' accepts.

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 states a specific verb and resource ('List companies'), so the agent immediately knows this is a read/list operation on the company collection. It does not distinguish itself from siblings like mautic_get_company or mautic_create_company, but the core purpose is unambiguous.

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?

There is no when-to-use guidance, no mention of how this differs from mautic_get_company for fetching a single record, and no note about pagination strategy or when to prefer search-based siblings. The agent is left to infer all routing decisions.

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