Tabla Calendar & Lore

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

Only states the tool browses content, with no disclosure of behavioral traits like pagination, default limits, or what happens on empty results. No annotations exist, so the description bears full burden, which it fails to meet.

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?

Two concise sentences that avoid verbosity. Each sentence adds value, but the structure could be improved by front-loading key information or using bullet points for parameters.

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?

Despite 8 parameters and no output schema, the description is incomplete. It does not explain default behavior, required formats for query/topic/category, or how results are returned, leaving significant gaps for an agent.

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 description explains only the 'mode' parameter, mentioning its enum options. With 0% schema coverage, it does not compensate for the other 7 parameters (day, month, year, limit, query, topic, category), leaving their meaning unclear.

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 browses a calendar and lore for tabla, specifying events, festivals, and facts. However, it does not differentiate from sibling tools like explain_taal or glossary_lookup, which also provide related content.

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?

No guidance on when to use this tool versus alternatives. It only describes basic operation without context on appropriate scenarios, such as when to choose events vs festivals vs facts.

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