pbi_list_page_presets

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds domain context about what a preset represents, but does not disclose any additional behavioral traits such as filtering, pagination, or response size.

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 two concise sentences in Spanish. It front-loads the primary purpose and then clarifies the meaning of a preset, with no redundant words or irrelevant details.

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?

For a zero-parameter read-only list tool with an output schema, the description is sufficiently complete. It explains what is returned (presets with blocks) and the underlying concept, though it does not detail how presets might be used in page composition workflows.

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 tool has zero parameters, and the description correctly focuses on what the tool returns rather than argument details. With no parameters to document, the baseline of 4 applies; the description adds conceptual clarity about preset intentions.

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 clearly states the tool lists available page presets with their component blocks. It also defines the concept of a preset as a page intention, distinguishing this from other listing tools like pbi_page_building_blocks or pbi_list_themes.

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?

The description implies this tool is used to browse preset page layouts before composing a page, but it does not explicitly mention when to use it versus alternatives. No exclusions or direct comparisons to sibling tools are provided.

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