danceflow_check_releases

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is known. The description adds that results are fetched fresh and that no installation or deployment side effect occurs, which is real added value, but it says nothing about how the "installed" input affects comparison or what the response contains beyond the output schema.

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?

It is a single short sentence with no filler, which is good, but the phrasing is compressed to the point of ambiguity ("optional observations"). Front-loading the query verb works; the trailing clause is unclear rather than economical.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The remaining gap is the unexplained "installed" parameter and the vagueness of "afresh" — for a one-parameter tool this is a modest but real omission.

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 single parameter "installed" has 0% schema description coverage, so the description carries the full burden — and it does not explain the parameter at all. "Optional observations" is the only hint and it does not map clearly onto an object map of string values, leaving an agent to guess its shape and purpose.

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?

"Query official stable releases afresh" gives a concrete verb and resource, and the clause about never installing or deploying packages distinguishes it from siblings like framerudiments_presets_install. The second half ("optional observations") is cryptic and blurs an otherwise specific statement.

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 a partial when-not signal ("never install or deploy packages"), but no positive guidance on when to call this versus siblings such as danceflow_capabilities or the various list/status tools. "Afresh" hints at bypassing cached data but the condition that would make an agent choose this tool is left implicit.

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