get_constraints

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

No annotations are provided, so the description bears the full burden. It discloses that it returns dimension values with Thai/English labels, time range, and explains the Buddhist Era conversion. It could mention whether the operation is read-only or idempotent, but overall good disclosure.

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 sentences that are front-loaded and concise: first states what it does, second adds usage guidance and a conversion note. No wasted words.

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 output schema, the description adequately explains the return value (dimension values, labels, time range) and provides a conversion note. It does not detail the output structure but is sufficient for an agent to understand its purpose. Slight improvement could be made by hinting at the output format.

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 coverage is 100% with a parameter description and example. The description adds context about the output but does not further explain the dataflow_id parameter beyond what the schema provides. Baseline 3 is appropriate.

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 gets 'all valid dimension values (with Thai/English labels) and the available time range for a dataflow', specifying verb and resource. It distinguishes from siblings like get_data (which retrieves actual data) and discover_dataflows (which lists dataflows).

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 indicates this tool is used to retrieve constraints needed to build a get_data query, providing clear context. However, it does not explicitly state when not to use it or mention alternatives, though the context is sufficient.

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