DataDistributionTool

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

No annotations exist, so description must handle transparency. It notes automatic field detection, value distribution calculation, and numeric grouping, but does not specify side effects or read-only nature. Some behavioral context is provided.

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 relatively concise with a few sentences covering key points. It could be slightly more structured, but it is clear and front-loaded.

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?

No output schema exists, and the description does not explain return values or output format. It covers the tool's purpose and capabilities but leaves gaps in what the agent can expect as result.

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?

Schema description coverage is 100%, so baseline is 3. The description adds context about single vs. comparative analysis (mapping to selectionTimeRange and baselineTimeRange) but does not explain parameters beyond schema.

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 analyzes data distribution patterns and field value frequencies in OpenSearch indices, distinguishing it from siblings like CountTool or SearchIndexTool. It specifies both single and comparative analysis modes.

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 mentions use cases (anomaly detection, data quality, trend analysis) and gives a concrete example (failures over time). However, it lacks explicit guidance on when not to use or alternatives.

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