sf_tooling_get_apex_class

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

With no annotations, the description carries full responsibility for behavioral disclosure. 'Fetch' implies a read-only operation, but the description does not explicitly state that it is non-destructive, mention permission requirements, or describe behavior for missing classes or errors. Minimal behavioral context is provided.

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 with no superfluous words, placing the action and key target first. It is appropriately sized and front-loaded, earning a high score for conciseness.

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 three parameters, no annotations, and no output schema, yet the description only covers the basic fetch operation. It does not explain the purpose of directory and targetOrg, the return structure, potential errors, or any limitations, making it under-specified for reliable agent use.

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%, so the description must compensate. It explains 'className' implicitly via 'by class name,' but the parameters 'directory' and 'targetOrg' are left entirely unexplained. The description fails to add meaning for two of the three parameters.

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 (Fetch), the resource (ApexClass metadata and body), and the method (by class name via Tooling API), effectively distinguishing it from more generic query tools like sf_tooling_query.

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 implies usage for retrieving a specific ApexClass but provides no explicit guidance on when to use this vs. alternatives such as sf_tooling_query, nor any when-not-to-use conditions. The purpose is clear enough to infer the use case, but exclusions are missing.

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