query_records

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it discloses that SOQL SELECT/WHERE/ORDER BY/LIMIT are executed and that results come back as JSON. It does not mention pagination or query limits, which keeps it from a 5.

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?

Front-loads the core purpose and the exclusion before the implementation detail. Some redundancy – the caps-lock SINGLE/ONE/IMPORTANT and the SOQL clause sentence restate earlier content – but every sentence is functional.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description supplies the routing, prerequisites, and query-capability context an agent needs. Minor gap: no mention of result limits or default-org resolution for targetOrg.

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 reported at 0%, so the description must carry parameter meaning. It does convey the WHERE/ORDER BY/LIMIT clause semantics and the prerequisite for knowing the SObject, but it says nothing about targetOrg (default org behavior) or the shape of selectClause beyond what's obvious. Partial compensation only.

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?

States a specific verb+resource (query records from a SINGLE Salesforce object) with scope and gives concrete examples of conditions. It explicitly names the sibling it is not (search_records for cross-object text search), so the agent can disambiguate without opening either schema.

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?

Gives explicit when-to-use (precise queries on one object with field criteria), when-not (text searches across multiple objects), the named alternative, and a sequencing prerequisite (run sobject_list first, optionally sobject_describe). Nothing is left to inference.

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