get_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Fetch', which implies a read-only operation, but it does not mention any limits, mutual exclusions, or response structure. The output schema covers return format to some extent, but behavioral traits are otherwise undisclosed.

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 a single short sentence, which is concise and front-loaded. It avoids unnecessary details, though it lacks structural elements like usage examples. Every word contributes to the core meaning.

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?

The tool has five parameters with mutual exclusions and a set of related sibling tools. The schema is detailed and an output schema exists, so return values are covered. However, the description does not provide overarching context or guidance on how to combine with other tools, making it minimally adequate but not complete.

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?

The input schema has 100% coverage with descriptions for all parameters, so the description adds little beyond the schema. It mentions 'one or more SINIM variables' which aligns with the 'codes' parameter, but does not clarify other parameters or their relationships.

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 uses a specific verb 'Fetch' and identifies the resource as 'municipal data for one or more SINIM variables', which clearly states the tool's function. It doesn't explicitly differentiate from sibling tools like preview_data or export_data, but the name 'get_data' and the description imply core data retrieval.

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?

There is no guidance on when to use this tool versus alternatives such as search_variables or preview_data. The description provides no context about appropriate use cases, exclusions, or selection criteria among sibling tools.

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