salesforce_describe_object

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'Return', which implies a read-only operation, but it does not state safety, permissions, or side effects. This is a minimal disclosure that does not proactively inform the agent about constraints or risks.

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 a single, clean sentence that is front-loaded with the core purpose. It has no wasted words, though it is so brief that it borders on under-specification, which is more penalized in other dimensions.

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 has an output schema, so return value description is not strictly necessary, but the description still lacks essential context about parameters and when to use the tool. For a simple describe operation, the description is too sparse to fully prepare the agent, especially given the absence of annotations.

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 description coverage is 0%, and the description does not explain the meaning or format of 'object_type' or 'org'. With two parameters and no guidance, the agent is left to guess what values to provide, making this a significant gap.

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 specifies the action ('Return') and the resource ('field/metadata information for a Salesforce object'), which distinguishes it from data retrieval tools like salesforce_query. However, it doesn't explicitly differentiate from sibling tools such as salesforce_list_objects, which also deals with objects, so it falls short of a 5.

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 no information about when to use this tool versus alternatives like salesforce_list_objects or salesforce_query. There is no mention of typical use cases, prerequisites, or exclusions, leaving the agent without guidance on tool selection.

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