streamelements_status

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

With no annotations, the description must carry the behavioral burden. It does disclose the scope of the check (account, credits, connection), and a zero-parameter "status" query naturally reads as side-effect free, but it says nothing about what a not-ready result looks like or what the agent should do about a failed connection.

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 compact sentence with the resource list up front and no filler. The colon-separated enumeration is slightly awkward and the Cotlet.dev branding adds noise, but nothing needs cutting.

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 trivial zero-parameter probe with no output schema, the description covers what is inspected but not what the result means or how to act on a negative outcome. It is adequate to call correctly, but thin on interpretation guidance.

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 no parameters, so there is no parameter meaning to convey and the baseline is 4. The description correctly avoids inventing inputs for a parameterless call.

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?

"Check" plus three named subjects (account, credits, StreamElements connection) tells the agent this is a readiness/health probe, which is clearly distinct from the action-oriented siblings (read, open, click, type, close). It loses a point because "ready" is never defined and the "Cotlet.dev account" framing is ambiguous about what is actually being checked.

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 no explicit statement of when to call this versus streamelements_read or streamelements_guide, and no mention of it being a prerequisite check before the other tools. The word "ready" only implies it should be run first; that routing decision is left entirely to inference.

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