get_pbir_page

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

With no annotations, the description carries the full burden of behavioral transparency. It states what is returned but does not disclose that this is a read-only operation, any error behavior, or details about the output format. The description adds little beyond a restatement of the purpose.

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?

Two concise sentences: the first states the main function, the second clarifies the page parameter. No unnecessary words, effectively front-loaded and easy to parse.

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 no output schema and no annotations, the description must explain return values and behavior more fully. It mentions page.json and visual names/types but does not elaborate on the structure, potential errors, or the role of pbirSessionId, leaving the agent with a vague understanding of the tool's output.

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 description's 'page = the GUID name or the displayName' duplicates the schema description for the page parameter, adding no new meaning. The pbirSessionId parameter is left unexplained in both schema and description, and with 50% schema coverage the description fails to compensate for the missing parameter semantics.

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 gets one PBIR page's page.json plus the names/types of its visuals. This is a specific verb+resource+output pattern that distinguishes it from siblings like get_pbir_visual (which gets a single visual) and list_pbir_pages (which lists pages).

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 usage: you need one specific page's JSON and its visuals. However, it doesn't explicitly say when to use this over alternatives (e.g., list_pbir_pages or get_pbir_visual) or mention any exclusions or prerequisites beyond the required params.

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