togoid_getAllDataset

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

No annotations were provided, so the description carries the full burden. It adequately describes the returned data structure (dictionary mapping dataset keys to configuration objects) and the fields included (label, regex, prefix, examples). It does not mention authentication or rate limits, but as a simple read-only list operation, this is not critical.

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 concisely structured with a clear opening sentence, bullet points for key fields, and a separate section for usage guidance. It is front-loaded with the main purpose and avoids unnecessary detail.

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 tool has zero parameters and an output schema, the description fully explains the return format and provides examples of usage. It covers discovery, ID format validation, and example finding, making it complete for a simple list tool.

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?

There are no parameters (schema coverage 100% with zero params), so baseline is 4. The description adds value by detailing the return structure and fields, which is beneficial for an agent.

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's purpose: listing all databases registered in TogoID with their ID formats. It explicitly mentions the verb 'list' and the resource 'databases', and distinguishes itself from siblings like 'togoid_getDataset' by implying a bulk operation.

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 explicitly states when to use this tool: for discovering available databases, checking ID format, and finding example IDs. It also suggests using 'countId' before bulk conversion, providing guidance on alternatives.

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