media.provider.status

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

With no annotations, the description carries the behavioral transparency burden. 'Read' establishes a non-mutating operation, and 'without paid generation' clarifies that no costly generation side effect will occur. It does not detail return values or possible error modes, but for a zero-parameter status check the key behavioral traits are 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?

The description is a single six-word sentence with no filler. It front-loads the core action ('Read provider readiness') and appends the cost-relevant qualifier ('without paid generation'), making every word purposeful.

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 zero-parameter read-only status tool, the description is largely complete: it says what the tool reads and that it does not trigger paid generation. However, because there is no output schema and no annotation support, the description could more explicitly describe what the returned readiness data looks like (e.g., per-provider states, booleans, or error conditions).

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?

The tool has zero parameters, so there is no parameter surface to document. The schema coverage is effectively complete, and the description adds no parameter-specific meaning because none is needed.

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 clearly states a specific verb ('Read') and resource ('provider readiness'), and the qualifier 'without paid generation' distinguishes it from the generation-focused sibling tools. It is immediately apparent what this tool does and how it differs from media.image.generate, media.video.generate, and media.job.status.

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?

'Without paid generation' implies this tool is a safe pre-generation check that does not incur costs, but it does not explicitly say when to use it versus alternatives, nor does it name any sibling tools. The usage context is implied rather than explicit.

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