get_record

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

With no annotations, the description carries full responsibility. It discloses the retrieval action but does not mention error handling, field selection, or whether it returns all fields. For a simple get-by-ID, this is moderately acceptable but lacks deeper behavioral detail.

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 concise with two sentences and an Args section. It is front-loaded with the main action. However, the Args section could be integrated more smoothly, and there is no structural hierarchy. Still, it is efficient and clear.

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 retrieval tool with no output schema and minimal parameters, the description is fairly complete. It explains the parameters but does not cover return format or error scenarios. Given the low complexity, it meets a minimum viable level but could add more context about potential issues or limitations.

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 has 0% description coverage, so the description must add meaning. It specifies that object_name is 'The name of the Salesforce object' and record_id is 'The ID of the record to retrieve,' which goes beyond the schema's property titles. This adequately compensates for the lack of schema descriptions.

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 'Retrieves a specific record by ID,' using a specific verb and resource. It distinguishes from sibling tools like create_record, delete_record, update_record, which have different actions.

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 vs alternatives, such as run_soql_query or get_sobject_fields. The description only states what it does, without context on limitations or when not to use it.

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