smartsuite_list_applications

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

Beyond the already-present readOnlyHint=true annotation, the description reveals that limit is enforced client-side because the API ignores it, and that the response includes a total count. This adds useful behavioral context about the actual behavior of the limit parameter.

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 sentences covering purpose, filtering, return shapes, and a performance warning. Every sentence earns its place, with no redundant or vague wording.

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 list tool with no output schema, the description adequately covers both return shapes and the total count. It could be improved by mentioning whether pagination (e.g., offset) is supported, but it already explains the limit behavior and provides enough for most usage.

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?

All three parameters have schema descriptions (100% coverage). The description adds further value by explaining the effect of slim (compact vs full objects) and the client-side enforcement of limit, which are not in the schema. The explanation of slim's recommendation for multi-table solutions is particularly helpful.

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 starts with 'List SmartSuite applications (tables)', a clear verb+resource pair. It distinguishes from sibling list tools like smartsuite_list_forms and smartsuite_list_automations by specifying the resource type and noting optional filtering by solution.

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 provides actionable guidance by noting the default 'heavy' return and recommending the slim:true option for multi-table solutions to avoid token budget issues. It does not explicitly state when not to use the tool or compare to alternatives, but the context is clear enough.

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