billing_provider_create

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

Annotations already declare readOnlyHint=false and destructiveHint=false, covering the basic safety profile. The description adds no behavioral context beyond that: no auth requirements, no uniqueness/duplicate-name behavior, no statement about what is created or returned.

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?

Three words is not conciseness but under-specification; the single fragment is front-loaded but earns no informational value beyond the tool name.

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 mutation tool with no output schema, zero schema coverage, and three undocumented parameters, the description is far too thin. It does not tell the agent what is required (the 'name' field) or what constitutes a valid provider.

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% and the description mentions no parameters. The three fields (name with min/max length, loginUrl, faviconLink) are entirely undocumented, leaving the agent to guess formats and constraints.

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?

States a verb and a resource ('Create infra provider'), so the operation type is clear. However, the resource is named 'infra provider' while the tool and siblings are named 'billing_provider_*' and a separate 'billing_node_create' exists, so the agent cannot be confident whether this creates a billing provider or a node-level infra entity.

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 when-to-use guidance at all. Nothing distinguishes this from billing_node_create or tells the agent what preconditions (e.g., existing provider listing via billing_providers_list) must hold before creating.

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