oral_history_resources

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

No annotations provided. Description only states it provides resources and is a 'DEMO', which hints at limited functionality but doesn't disclose specifics like data format, access methods, or rate limits. Minimal behavioral context.

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?

Single sentence, no fluff. Clearly states purpose and scope. The 'DEMO' tag adds a note but could be integrated or clarified. Otherwise efficient.

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?

Simple tool with no parameters and an output schema. Description provides domain scope but is vague on what 'archives and preservation resources' entails. The output schema likely fills in details, but the description alone is minimal for a complete understanding.

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?

No parameters (input schema empty, 100% coverage). With zero params, schema already fully documents the inputs. Description adds domain and scope (Kenya/East Africa), which is helpful but not essential for parameter understanding.

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 it provides 'oral history archives and preservation resources' for Kenya and East Africa, distinguishing it from sibling tools like cultural_heritage_sites or historical_documents. However, the 'DEMO' suffix may confuse whether the tool is fully functional.

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?

Implied usage: to fetch oral history resources for Kenya/East Africa. No explicit when-to-use or when-not-to-use compared to sibling tools. Lacks guidance on prerequisites or alternatives.

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