pbi_measure_dependencies

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

No annotations exist, yet the description offers no behavioral context: no mention of read-only nature, permissions, or potential cost. The description carries the full burden for transparency and fails.

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 a single sentence, front-loaded and to the point. It is concise but at the expense of important details, so while efficient, it is not optimally informative.

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 existence of an output schema and two optional parameters, the description is incomplete. It fails to explain filtering capabilities or return value structure. For a straightforward query tool, more context is expected.

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%, but the description does not explain the two parameters (table and measure) or their role as optional filters. The parameters are completely undocumented beyond the 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?

The description states the tool returns dependency graph rows from DISCOVER_CALC_DEPENDENCY, clearly indicating the resource and action. However, it does not explicitly differentiate from sibling tools like pbi_detect_circular_dependencies, though the specific verb 'return' and data source hint at its distinct role.

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 is provided on when to use this tool versus alternatives, no prerequisites, no exclusions. The description is purely functional.

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