insee_get_data

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

With no annotations, the description carries the behavioral disclosure burden. It does state that this is a read ('Get') and that it returns a TimeSeries, and it discloses inclusive period filtering. It does not mention idbank format requirements, ordering, pagination, or error behavior, but for a simple read tool the basic behavior is covered.

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 compact, front-loaded with the core purpose, and uses a clean Args/Returns structure. Each line adds semantic value and there is no filler.

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?

For a simple tool with one required parameter and three optional filters, the description covers the inputs and the return type. It is complete enough for an agent to call correctly, though it could optionally point to insee_search_indicators for finding an idbank.

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 0%, so the description must carry parameter meaning and does: idbank is the INSEE IDBANK identifier, start/end period are inclusive optional filters, and last_n limits to the last N observations. This adds meaning beyond the raw types in the schema, though it omits period format details.

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 opening line names the verb ('Get'), the resource ('time series data'), and the domain ('INSEE indicator'), so the tool's purpose is immediately clear. The mention of 'time series data' distinguishes it from sibling metadata/search tools, though it does not explicitly name an alternative.

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 implies usage: provide an idbank to retrieve time series, optionally filtered by period or limited to last N observations. It does not state when to prefer this tool over insee_get_indicator_metadata or insee_search_indicators, nor does it mention any prerequisites.

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