sf_execute_named_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states 'execute' without indicating whether the operation is read-only, what mutations may occur, whether it requires specific permissions, or what errors might arise. This is minimal and insufficient for an agent to anticipate side effects.

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, front-loaded sentence with no wasted words. However, it is so terse that it lacks essential contextual information, making it 'under-specification' rather than ideal conciseness. It earns a 4 for structure but loses a point for being overly minimal.

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 that there are 4 parameters (including a nested object), no output schema, and no annotations, this one-sentence description is grossly incomplete. An agent would not know what 'directory' or 'parameters' refer to, what the tool returns, or when to invoke it compared to other query tools.

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 only mentions 'query API name' (mapping to queryApiName). It does not explain 'directory', 'targetOrg', or the nested 'parameters' object, leaving the agent without any semantic understanding of these fields. The description adds partial value for one parameter but fails to compensate for the rest.

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's function: it executes a Salesforce Named Query API resource, identified by query API name. This is a specific verb+resource combination that distinguishes it from sibling tools like sf_query_org (SOQL query) or sf_execute_anonymous_apex (Apex execution).

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 guidance on when to use this tool versus alternatives such as sf_query_org, sf_search_org, or sf_execute_anonymous_apex. There is no mention of preferred use cases, prerequisites, or when it should not be used.

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