pbi_build_executive_page

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

The annotations show readOnlyHint=false, but the description does not clarify what side effects building a page has (e.g., whether it creates a new page, overwrites an existing one, or requires specific model state). No behavioral traits beyond the annotation are disclosed.

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, but this is under-specification rather than conciseness. It lacks essential information about the tool's behavior and parameters, so the single sentence does not earn its place as an adequate description.

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 complexity of a build tool with 6 parameters and no schema coverage, the description is severely incomplete. It does not explain what the page building entails, how parameters affect the output, or any dependencies, making it insufficient for an agent to 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?

With 0% schema description coverage and 6 parameters, the description fails to explain any of them. It mentions 'fila de KPIs' and 'grafico protagonista' but does not connect these to the 'measures' or 'category' parameters, leaving the agent unable to infer parameter meanings.

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 'Pagina de resumen ejecutivo: fila de KPIs y grafico protagonista' gives a vague idea that the tool produces an executive summary page with a KPI row and a featured chart, but it uses a noun phrase rather than a clear verb, so it doesn't explicitly state what the tool does. It implies building, but doesn't distinguish from sibling tools like pbi_build_dashboard or pbi_compose_page.

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?

There is no guidance on when to use this tool compared to alternatives. No context, prerequisites, or exclusions are provided, leaving the agent without direction on selecting it over similar page-building tools.

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