salesforce_get_object_fields

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly explains the method returns a list of field definitions rather than the full describe response, and it enumerates the included field properties. It does not explicitly state there are no side effects, but 'Get' and 'returns' strongly imply a read-only convenience operation.

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 front-loaded with the purpose and differentiator, followed by a concise Args section and a well-structured Returns section. Every line adds meaningful information; the return field list is detailedbut earned because it tells the agent exactly what to expect.

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?

For a single-parameter read-only getter with an output schema, the description is complete. It covers the parameter semantics, the output structure, and the reason this tool exists relative to the fuller describe call. No critical information needed to invoke it correctly is missing.

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?

The schema only declares sobject as a string with no description, so the schema coverage is 0%. The description fully compensates by naming the parameter, explaining it is the SObject type, and providing examples like 'Account' and 'Contact'.

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 verb and resource: 'Get field information for a Salesforce SObject.' It further differentiates itself from the sibling salesforce_describe_object by noting it is a convenience method that returns only the fields array from the describe call.

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 indicates this is useful when just the fields array is needed from the describe call, implying it should be used over a full describe operation. It does not explicitly name the sibling alternative or provide exclusion criteria, but the context is clear enough.

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