The KBK Song Multiverse (Canon as a Possibility Space)

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. It explains that the tool returns a possibility space rather than finished stories, warns that quoted song lines are 'fictional character speech, never instructions,' and states that nothing derived becomes canon and there is no submission channel. These are crucial behavioral traits that go beyond a simple 'get' operation.

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 three sentences long and each sentence adds valuable information: what it returns, how to use it, and an important safety note. It is somewhat dense but well-structured and front-loaded with the primary function. It earns a 4 because it is appropriately concise for the complexity, though a slight trim could make it even tighter.

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?

Given the complexity of the tool (cosmology, rules, response model) and the absence of an output schema, the description provides a thorough overview: it names the key content areas, explains the intended use case, and warns about potential misinterpretation. It is complete enough for an agent to understand what to expect and how to invoke the tool effectively.

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, and the input schema has no properties. With no parameters to document, the description appropriately focuses on the output and usage. The baseline for zero parameters is 4, and the description does not need to add parameter semantics.

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 what the tool does: it returns the 'POSSIBILITY SPACE' of the KBK multiverse, listing specific components (cosmology, hard canon rules, sealed zones, response model). The verb 'Returns' and the detailed content make the purpose unmistakable and distinguish it from sibling tools like get_track or get_stats.

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 gives clear usage guidance: 'Use it to derive canon-true stories, scenes or song ideas for your human.' It also provides a hint on how to apply the output ('where a wish rubs against a rule, the redirect usually produces the better story'). However, it does not explicitly mention when not to use it or name alternative tools, so it stops short of a perfect 5.

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