get_report_visuals

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

No annotations provided, so description carries burden. States it 'gets all visuals' implying read-only, but does not disclose permissions, error handling, or behavior if page missing. Adequate but minimal beyond 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?

Very concise; one-line purpose followed by compact Args section. Every sentence adds value. Front-loaded with purpose.

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?

Tool is straightforward; output schema exists, so return details not needed. Description covers essential input context. Could mention that it returns a list/array of visuals, but not necessary given schema.

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?

Description lists all three parameters with additional context: page_name's source (from get_report_pages), workspace_id's optionality. Schema has 0% coverage, so this adds meaning over the schema's simple type definitions.

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?

Clearly states 'Get all visuals on a specific page of a Power BI report'. Verb 'get' and resource 'visuals on a page' are specific. Distinguishes from sibling tools like get_report_pages (gets pages) and execute_dax_query (query).

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?

Explicitly mentions that page_name 'comes from get_report_pages', providing context for prerequisite tool. Does not explicitly state when not to use, but the context is clear. Minor omission of exclusion criteria.

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