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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description adds no behavioral context about the read itself; the sentence about MCP approval requirements and business workflow approvals is boilerplate that introduces approval concepts irrelevant to a read operation and could confuse the agent.

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 first sentence is efficient and front-loaded. The second sentence about approval configuration does not earn its place in a read tool's description and reads as unrelated boilerplate.

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 tool with rich annotations and an output schema (so return values needn't be described), the description covers the essentials: what it reads and by which key. The irrelevant approval sentence is noise rather than a fatal gap, but it slightly muddies completeness.

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?

There is a single 'id' parameter with 0% schema description coverage, but its type, UUID format, and pattern fully constrain the value. The description's word 'record' implies the id selects a record, adding marginal meaning beyond the schema but nothing about expected id source or failure modes.

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 first sentence states a specific verb and resource ('Read a criteria_profile record'), which is clearly distinct from create/update/delete/activate/archive siblings. It doesn't explicitly name list_criteria_profile as the multi-record alternative, but the singular 'record' implies single-item retrieval.

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?

There is no guidance on when to use this versus list_criteria_profile or any other retrieval sibling, nor any prerequisite information. The only additional sentence concerns approval configurability, which does not help the agent decide when to call this tool.

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