pbi_disable_card_autoscale

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

With no annotations, the description carries the full burden. It discloses the properties set but fails to mention side effects, reversibility, or the role of the required parameter 'extract_folder' (which appears unrelated to autoscale). The agent lacks behavioral context for safe invocation.

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 a single, technically precise sentence. It is concise but could be improved by listing parameters or breaking into multiple sentences for clarity. No redundancy, but the technical detail is dense.

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 tool has 4 parameters (1 required) and 0% schema coverage, the description is incomplete. It does not explain how to use extract_folder, page, or visual_ids to target specific card visuals. The output schema exists but does not compensate for missing parameter semantics.

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?

Schema description coverage is 0%, so the description must explain all parameters. It only hints at label_precision via the technical note, but extract_folder (required), page, and visual_ids are entirely unexplained. The agent cannot infer their purpose from the description alone.

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 disables auto K/M/B unit-scaling on card visuals, specifying the underlying settings (labelDisplayUnits=1 and labelPrecision). This verb-resource pair is specific and distinguishes it from other PBI formatting tools.

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 for card visuals needing to disable autoscale, but it does not provide explicit guidance on when to use this tool versus alternatives like pbi_set_format or pbi_set_visual_format_property. There are no when-not-to-use or alternative tool references.

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