danceflow_capabilities

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered by structured data. The description adds one piece of genuine behavioral context beyond that: "observed runtime availability," which tells the agent the response includes live status rather than static metadata. It does not say whether unavailability is reported per component or as a summary.

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 sentence with zero filler, front-loading the verb and the scope. Nothing in it is redundant with the tool name or could be cut without losing information.

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 zero parameters and an output schema present, the description need not explain return values, and it covers the scope of what is enumerated. A note on whether this is the recommended first call in the danceflow family would make it fully complete, but nothing required to invoke it correctly is missing.

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, so there are no semantics to clarify and the baseline of 4 applies. The description correctly implies a no-argument, whole-inventory call rather than suggesting any filtering.

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?

"Discover all 17 components, their MCP tools, references and observed runtime availability" names a specific verb (Discover) and enumerates the resources returned, so an agent knows exactly what this yields. It stops short of naming siblings such as danceflow_component or danceflow_search, so the boundary between 'discover everything' and 'fetch one component' is inferable but not stated.

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 when-to-use or when-not-to-use statement. The word "Discover" plus "all 17 components" implies this is the entry-point/inventory call before drilling into danceflow_component, but that routing is left to the agent to infer rather than stated.

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