Create List View

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the write nature is clear. The description adds context that list views appear in the object's selector and serve as shared filters, but it doesn't disclose permissions, side effects, or creation behavior beyond what annotations convey. This is adequate but not rich.

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-loaded with the primary action, and each sentence adds value: the first states what it does, the second explains the concept and use cases. No waste or redundancy.

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?

Given the tool has 8 parameters and nested objects, the description provides a solid high-level orientation and purpose. It does not detail configuration steps, but the schema thoroughly documents all parameters. The mention of 'sorting' is slightly inaccurate since no sort parameter exists, but the overall context is sufficient for a create tool.

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%, and every parameter has a clear description in the schema (e.g., objectName, fullName, filters). The description adds a high-level mention of columns/filters/sorting but does not explain individual parameters beyond schema, so it meets the baseline but does not exceed it.

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 'Creates a List View for any Salesforce object' with a specific verb and resource. It explains what list views are and gives concrete examples ('My Open Cases', 'High Priority Leads'), distinguishing it from other create tools in the sibling list like sf_create_custom_object or sf_create_flow.

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 clear context on when to use the tool ('Use to create shared views...') with practical examples. However, it does not explicitly mention when not to use it or alternatives, so it misses the exclusion part for a 5.

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