pbi_list_roles

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

With no annotations, the description does not explicitly disclose whether the operation is read-only, requires special permissions, or has any side effects. It relies on the verb 'list' to imply safety but does not confirm it.

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?

A single short sentence that directly states the tool's function without superfluous words, achieving high conciseness for a simple list operation.

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 the purpose is clear, the description omits any explanation of the 'source' parameter and does not provide usage context or behavioral details. The presence of an output schema mitigates the need for return format, but the missing parameter semantics and usage guidance make it incomplete for a complex environment with many sibling tools.

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 includes a 'source' parameter with a default of 'live', but the description does not explain its purpose or possible values. Since schema description coverage is 0%, the description fails to add meaning to this parameter.

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 'Lista los roles de seguridad (RLS) y sus filtros por tabla' clearly identifies the action (list) and the resource (security roles/RLS filters), distinguishing it from sibling tools that list other model objects.

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 regarding when to use this tool versus alternatives like pbi_list_tables or pbi_audit_model. The description only states the function, leaving usage entirely implied.

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