List Custom Forms

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no pagination behavior, no note that results may be filtered, no indication of what the openWorldHint implies for result volume or ordering.

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 single phrase is technically concise but is under-specification rather than economy — there is no front-loaded content because there is no content beyond the tool title. Length is not the problem; absence of substance is.

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?

An 11-parameter filtered list tool with an output schema and a bare four-word description leaves the agent unable to use any filter or pagination argument meaningfully. The output schema excuses explaining return values, but nothing excuses the total absence of parameter and scoping information.

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?

Eleven optional parameters with 0% schema description coverage and zero mention in the description. Filter names, date-range operators (gt/lt/gte/lte), sort syntax, and page_size limits are all entirely undocumented, so 0% coverage gets no compensation whatsoever.

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?

Tautological: description restates name/title.

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?

There is no guidance on when to use this versus get_custom_form (single fetch) or the form-set/form-field listing tools. The agent must infer that this is the bulk-listing entry point entirely from the name.

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