Hackathon Rules

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

No annotations are provided, so the description must disclose behavior. It only says the tool is a 'digest' of rules, implying a summary, but does not explain whether it is read-only, what format the rules come in, or if there are any side effects. The burden is on the description, and it falls short.

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 a single, front-loaded sentence that immediately states the purpose and usage. Every word adds value, and there is no fluff or redundancy. It is efficiently structured.

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 zero-parameter, simple rules-digest tool, the description covers the essential information: what it provides and when to call. It does not describe the output format, but that is likely self-explanatory given the name. The description is sufficient for an agent to decide to invoke it, though more detail on the digest's content would raise it to a 5.

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, so the schema is empty. Per guidelines, a 0-parameter tool gets a baseline of 4. The description doesn't need to add parameter details since there are none, and it correctly avoids mentioning nonexistent inputs.

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 the tool provides 'Bases/rules of the whole hackathon' and explicitly says 'Call when AI needs event rules.' It names the resource (rules) and the trigger condition. No sibling appears to cover the same function, so it stands distinct.

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?

It provides an explicit usage condition ('Call when AI needs event rules'), which tells the agent when to invoke it. It does not mention alternatives or exclusions, but given the specific condition and lack of similar siblings, this is adequate.

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