uof_custom_query_forms

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

With no annotations, the description carries full burden. It discloses scope (visible to current account), pagination (first page only), and default behavior. Does not explicitly state read-only or auth requirements, but given the context, the behavioral traits are adequately covered.

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?

Five sentences efficiently cover purpose, usage, and limitations. Front-loaded with the core action. No unnecessary words.

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 search tool with output schema, the description covers purpose, usage, parameter behavior, and limitations. It provides sufficient context for an AI to select and invoke correctly, especially given sibling tool context and output schema existence.

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 100% with descriptions, but the description adds valuable context: default date ranges (today, last 7 days), keyword fields, max_results default and practical limit. This exceeds the baseline 3 for high 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?

The description clearly states the tool searches UOF forms by date range and keyword, returning a list with TaskId. It distinguishes from siblings by positioning itself as the entry point to obtain TaskId for use with get_task_data/get_task_result.

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?

Explicitly states when to use (user lacks TaskId and wants to list recent forms or search keywords). Provides alternative, mentions it fills a gap, and gives limitation about only first page, suggesting narrowing date/keyword for precision.

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