jccdb_dataset_info

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

The description adds useful context (dataset size, open nature) beyond annotations that already declare readOnlyHint and destructiveHint. No contradictions; the description supplements the safety profile.

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 (bilingual) that front-load the purpose and provide key details without waste. Every sentence earns its place.

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 no parameters and no output schema, the description fully explains the tool's output and its context (65k Japanese construction items, primary data source). Complete for a simple info 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?

No parameters exist, so schema coverage is 100% trivially. The description compensates by detailing what will be returned (metadata, scale, license, etc.), fulfilling the need for output guidance.

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 returns metadata, scale, license, download links, and citation for the JCCDB dataset, distinguishing it from sibling tools that handle cost estimation or price lookups.

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?

Explicitly says 'Use when looking for a primary construction-cost data source.' Provides clear context but does not mention exclusions or alternatives, though sibling names imply when not to use.

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