pbi_list_tables

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

No annotations are provided, so the description carries the full burden. It only states 'List model tables and columns' with no mention of side effects, read-only nature, prerequisites, or what the parameters do. For a tool with two parameters and no safety cues, this is severely lacking.

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 extremely short (one sentence) and does not waste words, but it omits critical information. It is under-specified rather than concise, forcing the agent to guess about parameters and behavior.

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?

While an output schema exists (not shown), the description fails to cover essential aspects: parameter behavior, prerequisites, or when to use. The tool has two optional parameters that significantly affect output, and the description provides no context about them.

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%, and the description does not mention any parameters. The agent must rely solely on parameter names ('include_hidden', 'include_row_counts'), which are slightly informative but insufficient. The description adds no value.

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 'List model tables and columns' clearly states the action (list) and the resource (model tables and columns). It distinguishes from sibling tools like pbi_list_measures or pbi_list_pages, which list different resources. However, it could be more explicit that it returns columns within each table.

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?

No guidance on when to use this tool versus alternatives. The sibling list is provided but without any contextual hints about when to choose pbi_list_tables over other list tools. The agent must infer from the name alone.

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