salesforce_describe_object

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

The readOnlyHint annotation is consistent with the non-destructive 'Get' description. The description adds useful context about the scope of metadata returned (all fields, relationships, field properties) beyond the annotation, though it does not detail error handling or special behaviors. No contradiction.

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 followed by two illustrative examples. Every word earns its place, with no redundancy or filler.

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 simple read-only describe tool with one fully documented parameter and no output schema, the description adequately conveys the tool's capabilities and return scope. The examples clarify usage without unnecessary detail.

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%, with the objectName parameter fully described including examples. The description's examples (Account, Case) duplicate the schema info and provide no additional semantic depth, so the baseline score of 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 the tool's function with a specific verb ('Get') and resource ('detailed schema metadata'), listing fields, relationships, and field properties. The examples ('Account', 'Case') reinforce the purpose and help distinguish it from query or management tools.

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 clearly indicates when to use this tool (when needing schema metadata). However, it does not explicitly mention alternatives or exclusions, though the context is unambiguous given sibling tools like salesforce_query_records. This merits a 4 rather than 5.

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