pbi_list_format_presets

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

With no annotations provided, the description carries the full burden. It correctly indicates the tool is read-only (returns a catalogue) and describes the case-insensitive matching behavior. However, it does not disclose details like return format or pagination, which could be inferred from the output schema but not stated.

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 extremely concise: two sentences with no redundant information. The main purpose is front-loaded, followed by a brief explanation of the optional parameter. Every word 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?

For a simple list tool with an output schema present, the description is complete. It covers the tool's purpose, the optional filter, and the filtering mechanism. No additional context is needed for an AI agent to use it correctly.

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 only parameter, filter_substring, is well-described: it is optional, matched case-insensitively against preset names. This adds meaning beyond the schema, which only specifies type and default. The description coverage is 0% in schema, so the description provides valuable semantic context.

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 it returns the catalogue of format-string presets, distinguishing it from sibling tools like pbi_apply_format_preset which applies a preset. The verb 'return' and resource 'catalogue' are specific.

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 explains the optional filter_substring parameter and its use case ('when an LLM only needs a subset'), providing clear guidance on when to use it. It does not explicitly state when not to use it, but the context is sufficient.

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