Describe Salesforce Object

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

The description adds behavioral context beyond annotations, such as the ability to include picklist values and choose response format. It also explains the type of metadata returned. No contradictions with annotations (readOnlyHint=true, etc.).

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 well-structured with separate sections for Args and Returns, front-loading the main purpose. It is moderately sized without excessive verbosity, though some redundancy exists (e.g., repeating field details).

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 description is thorough for a tool with no output schema, detailing return values (field names, types, required flags, picklist values). It fully covers all parameters and provides sufficient context for effective 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 coverage is 100%, and the schema already describes all parameters with examples and defaults. The description's Args section repeats similar information, adding little new meaning. Thus, baseline 3 is appropriate.

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 it gets metadata for a Salesforce object, listing specific details like field names and types. It distinguishes itself from siblings by explicitly indicating its use before writing SOQL queries or CRUD operations, which contrasts with querying or listing objects.

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 explicitly states when to use: 'Use this to discover what fields are available before writing SOQL queries or creating/updating records.' It provides clear context for its usage, though it does not explicitly mention when not to use or alternatives like salesforce_metadata_query.

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