forms_1

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds 'Fetches data. Makes no changes.' which confirms these but does not add new behavioral details. With rich annotations, the description adds minimal extra transparency. No contradiction.

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: three compact lines with an emoji, title, HTTP method, and a one-sentence summary. It is front-loaded with key identifiers and contains zero wasted text. Perfect for a simple list tool.

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?

The tool is a read-only list with well-annotated behavior, comprehensive schema, and no output schema to document. The description covers the core purpose and safety. It does not mention pagination or response format, but the schema handles pagination parameters, and the return value is implicit for a list. Adequate for the complexity.

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 100% description coverage, so the schema already documents all parameters (limit, offset, orders, filters). The description does not mention any parameters, and no additional meaning is provided beyond the schema. Baseline 3 is appropriate.

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 'List all forms' and includes 'Fetches data. Makes no changes.' The verb 'list' and resource 'forms' are specific, and the read-only hint reinforces the purpose. However, it does not explicitly distinguish from sibling tools like list_all_accounts or list_all_contacts, but the form-specific focus is clear.

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 implies when to use (list forms) and that it is read-only, but it provides no guidance on when not to use or alternatives. Given the straightforward nature of the tool, the implied usage is adequate but lacks explicit exclusions or context with siblings.

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