get_sdds_data

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

With no annotations provided, the description carries the full burden of behavior disclosure. It explains that the tool returns dynamic or static table data depending on the model, but it does not describe the return format, potential errors, pagination, or any operational constraints. This is adequate but lacks rich behavioral detail.

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 three sentences long, front-loaded with the primary purpose, and every sentence contributes meaningful information. There is no redundancy or fluff.

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 the tool's low complexity, full schema coverage, and no output schema, the description covers the essential workflow and parameter sourcing. However, it could be more complete by explaining what the returned data looks like or any limitations, especially without annotations.

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 already provides full descriptions for all parameters, so the baseline is 3. The description adds value by explaining that var_id and model come from list_sdds and by clarifying the meaning of the model enum ('data' vs 'statictable'), which goes beyond the schema's descriptions.

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 action ('Fetch actual SDDS indicator data') and resource, and further distinguishes behavior by model type ('For 'data' model, this fetches dynamic table data. For 'statictable' model, it fetches a static table.'). It also references the prerequisite list_sdds, setting it apart from listing tools.

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 explicitly instructs to use list_sdds first to obtain var_id and model type, establishing a clear workflow. It also explains the difference between the two model types, helping users decide when the tool is appropriate. However, it does not explicitly mention alternative data-fetching tools or when not to use this tool.

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