salesforce_manage_object

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

Notes that changes affect metadata and require proper permissions, which adds some behavioral context. But without annotations, it does not fully disclose potential risks like destructiveness of updates, rate limits, or error handling behavior.

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 concise, front-loaded with the main purpose, uses bullet points for clarity, and includes examples and a note on permissions. Every sentence serves a purpose with no 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?

Covers the main operations and prerequisites but lacks details on return values, error scenarios, or behavior of optional parameters. Given the complexity of 9 parameters and no output schema, more context would be beneficial.

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?

With 100% schema coverage, the description adds value by grouping operations, providing examples of usage (e.g., 'Create Customer_Feedback__c object'), and clarifying context beyond the schema (e.g., API name without __c suffix is implied).

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 it creates or modifies custom objects in Salesforce, lists specific operations (Create and Update), and differentiates from sibling tools like salesforce_manage_field or salesforce_describe_object.

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?

Provides clear context for when to use the tool (creating or modifying custom objects) and gives examples. However, lacks explicit guidance on when not to use it or mention of alternatives like salesforce_manage_field for field-level changes.

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