Get table dimensions and members

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

With no annotations provided, the description carries the full burden of disclosing behavior. It transparently mentions that large dimensions are truncated, which is a key operational trait, and states that member IDs are returned for use with another tool. This adds significant context beyond the schema.

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 exceptionally concise, consisting of just two sentences. It front-loads the purpose and delivers key operational details (truncation, filtering, and next-step usage) without any fluff or repetition.

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 simplicity (3 parameters, no output schema, no annotations), the description covers the critical context: the output structure, truncation behavior, and how to use the results. It could arguably mention the return format explicitly, but it is sufficiently complete for an AI agent to understand and invoke the tool correctly.

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 schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds value by giving a concrete example for member_filter ('gasoline') and explaining the rationale for truncation (related to max_members), enriching the parameter semantics beyond the schema's definitions.

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's purpose: to return the structure of a Statistics Canada table, specifically its dimensions and members with member IDs. This distinguishes it from sibling tools like get_data_by_coordinate, which retrieves data, and search_tables, which searches for tables.

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 provides practical usage guidance by explaining the truncation behavior and advising to use member_filter (e.g., 'gasoline') for finding specific members. It also connects to get_data_by_coordinate, suggesting a workflow. However, it lacks explicit 'when not to use' or direct alternatives.

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