sf_query_org

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

With no annotations, the description must carry this burden, but it only states the action. It does not disclose whether the query returns results, how it handles errors, rate limits, or side effects. It implies a read-only operation but does not confirm or provide additional behavioral context.

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 sentence, which is concise but under-specified. It does not provide enough information for a tool with three parameters and no supportive schema descriptions. It is not an 'appropriately sized' description because it omits essential usage and parameter context.

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 complexity (3 params, no annotations, no output schema), the description is incomplete. It does not explain what the tool returns, how to specify parameters, or when to use it. A one-line description is insufficient for this tool's context.

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 offers no explanation of the parameters (query, directory, targetOrg). The description adds no value beyond the schema, which itself has no descriptions, so the agent is left without meaning for each parameter.

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 action: 'Run a SOQL query against a Salesforce org.' It identifies the specific resource (Salesforce org) and the operation (SOQL query). However, it does not distinguish this from sibling tools like sf_query_org_paginated or sf_search_org, which also involve querying.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention when to prefer paginated queries, search, or named queries, nor any prerequisites or contexts. The description simply states the action without usage direction.

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