smartsuite_list_forms

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

Annotations declare readOnlyHint=true, so the tool is read-only. The description adds behavioral context by listing the specific fields returned (id, name, description, page count, etc.) and the usage scenario. It does not mention pagination or limits, but the read-only nature reduces the burden.

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 two sentences, front-loading the main purpose and returned fields, then adding context. Every sentence adds value, with no wasted 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?

With one required parameter, no output schema, and readOnlyHint annotations, the description explains the output fields and usage context. It lacks detail on error handling or pagination, but for a simple list operation, it is largely complete.

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 only parameter 'applicationId' is described in the schema as 'The application ID.' The description adds no new semantics beyond mentioning 'for a SmartSuite application.' Since schema coverage is 100%, baseline is 3; no additional value.

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 forms (form-type report views) for a SmartSuite application.' It specifies the verb 'List', resource 'forms', and provides context. It distinguishes from sibling tools like smartsuite_describe_form by detailing the returned fields and usage in ITSM dashboards.

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 forms are used for record submission and are launched from button-row widgets in ITSM dashboards, but it does not explicitly state when to use this tool versus alternatives like smartsuite_describe_form. No when-not-to-use guidance is provided.

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