modx_create_provider

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

No annotations are provided, so the description carries the full behavioral burden and mostly does not. It says nothing about required permissions (manager/administrative access), whether creation is idempotent or fails on duplicate names, whether credentials are validated at creation time, or what is returned. Only the paid-provider credential requirement is disclosed.

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 sentences with the core action first and the conditional second; no filler, no restatement of the name. Each sentence carries distinct information.

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 five-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition is under-specified. An agent cannot confidently determine auth requirements, duplicate handling, or the meaning of half the fields before calling it.

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% across five parameters, so the description must compensate and largely does not. It clarifies username and api_key as credential pairs for paid providers and hints 'modstore.pro' is a service_url sample, but 'name', 'description', and 'service_url' semantics and their relationship (label vs endpoint) remain undocumented.

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 ('Add a transport provider') and gives a concrete example ('modstore.pro'), which makes the intent immediately clear and separable from modx_list_providers / modx_update_provider / modx_delete_provider. It stops short of explicitly naming those siblings, so it sits at a clear-but-not-differentiated 4.

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 one real conditional: 'For paid providers pass username + api_key.' That tells the agent when to supply credentials, but there is no guidance on when to create versus update an existing provider, or what to do if a provider with the same name already exists.

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