Unused Custom Formats

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

No annotations are present, and the description only states it is an alias. It does not disclose any behavioral traits such as pagination, filtering behavior, or whether it is read-only. The agent gets no insight beyond the name.

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?

Extremely short but under-specified. It is not a model of conciseness because it sacrifices utility for brevity. Every sentence should earn its place, but this single sentence adds minimal value.

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 complexity (11 parameters, no output schema), the description is grossly inadequate. It provides no information about return format, pagination, expected behavior, or prerequisites. The agent cannot reliably invoke this tool from the description alone.

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 coverage is 0% and the description adds no meaning to any of the 11 parameters. Parameters like 'to', 'from', 'page', 'detail', etc. are entirely undocumented. The description does not compensate for the low schema coverage.

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 says 'Alias for custom format misses' which indicates it retrieves unused custom formats, but lacks a clear verb and does not specify the action (list, search, etc.). It is vague and does not distinguish from siblings like 'custom_format_hits' or 'duplicate_custom_formats'.

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 on when to use this tool versus alternatives. There are many sibling tools for custom formats and reporting, but no conditions or exclusions are provided.

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