Get Custom Formats

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

With no annotations provided, the description must disclose behavioral traits. It only states 'list', implying a read operation, but lacks details on pagination, filtering, side effects, or permissions. This is insufficient for an agent to understand the tool's full behavior.

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 short (one sentence) but at the cost of completeness. It fails to add any value beyond the tool's name and title, making it merely a repetition rather than a helpful elaboration. For a tool with 11 parameters and many siblings, more detail is needed.

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's complexity (11 parameters, no output schema, no annotations), the description is grossly inadequate. It provides no context about the returned data, filtering, or how to use the parameters effectively, making it nearly useless for an AI agent.

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 input schema has 11 parameters with 0% coverage (no descriptions in the schema), but the description adds no information about any parameter. It does not explain meaning, format, or usage of parameters like 'to', 'from', 'detail', 'fields', etc., leaving the agent without guidance.

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 'List custom formats' clearly states the action and resource, but it is essentially a tautology with the name and title. It does not distinguish this tool from many sibling tools related to custom formats (e.g., custom_format_hits, duplicate_custom_formats, update_custom_format).

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?

No guidance is provided on when to use this tool versus alternatives. The description gives no context for use cases, prerequisites, or exclusions, leaving the agent without direction among many similar tools.

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