ai_status

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

No annotations are provided, so the description carries the burden itself. It implies a read-only status query (no side effects are suggested), but never states whether it probes services live, whether it can be slow or require network/key configuration, or that results may be cached or stale.

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?

A single front-loaded sentence that leads with the answer ('What AI is available here') and then lists the categories. Dense but every clause adds a distinct piece of information about the returned content.

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 no output schema and no annotations, the description effectively documents the return value by enumerating the categories reported, including the 'online.ready: service -> tasks' shape. It is adequate for a simple read-only status tool, though the exact result format and meaning of 'the default one' remain slightly vague.

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 takes zero parameters (empty object schema), so there is nothing for the description to clarify beyond what the schema shows. Baseline 4 for a parameterless tool.

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 clearly that the tool reports which AI capabilities are available (background removal, inpaint backend, ComfyUI, online services, default), which is a specific information resource. It does not, however, distinguish itself from the similarly-named sibling ai_services, so an agent may hesitate between the two.

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 description only enumerates what the tool returns; it gives no when-to-use guidance, no prerequisites, and no comparison to the closely related ai_services or comfy_settings siblings. An agent must infer that this is a discovery/pre-flight call.

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