pbi_apply_format_preset

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

No annotations provided. Description states it applies presets to a list of items and lists supported families, but does not disclose overwrite behavior, error handling, or permission needs. The description adds moderate value beyond the schema.

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 focused sentences with no fluff. Front-loaded with the action, then explanation and examples. Each sentence earns its place.

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?

Despite an output schema (not shown), the description lacks prerequisites, return value description, and explicit handling of multiple items. Given 0% schema parameter coverage and no annotations, the description is insufficiently complete.

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, the description should elaborate on parameters. It lists preset families but does not describe 'names', 'table', 'preset', or 'object_type' beyond implying object_type can be measure or column. Incomplete for a 4-param tool.

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?

Description clearly states the tool applies a named format preset to measures or columns, with specific verb 'Apply' and resource list. Distinguishes from sibling pbi_set_format by noting it wraps that tool for convenience.

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?

Description advises using pbi_list_format_presets_tool to inspect presets and mentions it avoids memorizing raw format strings, but does not explicitly contrast with direct use of pbi_set_format or specify when to prefer this tool.

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