list_metadata

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

No annotations, so description must disclose all behavior. It explains output content (measures, dimensions, hierarchies) and fallback for cube_name. No hidden side effects noted.

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?

Well-structured with Args section, but somewhat lengthy. Could be more concise, though every sentence adds value.

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 output schema exists, return values are covered. Input behavior thoroughly explained. Lacks only minor details like error cases or permission requirements.

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 0%, but description fully explains both parameters: cube_name default behavior and dimension usage with example bracketed name. Adds significant value beyond schema.

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?

Describes specific action: listing queryable metadata of SSAS cube/tabular model for obtaining bracketed unique names. Distinguishes from sibling tools (execute_dmv, execute_query) as a preparatory step.

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?

Explicitly states to call before writing queries to avoid guessing names. Explains when to use dimension parameter. Does not mention when not to use but context is sufficient.

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