create_media_providers

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

Annotations already convey that this is a non-read-only, non-destructive, idempotent operation. The description adds the specific behavior that it adds a provider and shows the HTTP method and path, but does not disclose side effects, duplicate handling, authentication needs, or other behavioral details. No contradiction with annotations.

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 short and front-loaded with the core action. The endpoint and Args block are useful and not redundant with the schema, adding the HTTP path and parameter meaning without unnecessary prose. It is efficient, though slightly more structured than needed.

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 simple one-parameter tool with an output schema and informative annotations, the description covers the essential purpose and parameter. However, it omits context about what a media provider is, prerequisites, duplicate/idempotency behavior, and any caveats. It is adequate but leaves gaps an agent might need to resolve.

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%, so the description must carry parameter meaning. It does this by explicitly stating that 'url' is 'The URL of the media provider to add.' This adds real semantics beyond the schema's title/type. It does not clarify optionality or URL format constraints, but the schema's default null and zero required parameters cover optionality.

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 opens with 'Add a media provider.', a specific verb plus resource that immediately states the tool's function. The endpoint 'POST /media/providers' reinforces this and distinguishes it from sibling tools like list_media_providers, delete_media_providers_by_provider, and create_media_providers_refresh.

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?

The verb 'Add' implies the tool should be used when the agent wants to create a new media provider, but the description provides no explicit when-to-use or when-not-to-use guidance and does not mention alternatives such as refreshing or listing providers. Usage is implied rather than stated.

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