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

With no annotations, the description must disclose behavioral traits, but it only says 'load' and 'scoped' without explaining what scoping entails, whether the operation is side-effect-free, or how errors are handled. The lack of detail on return data or failure modes leaves the agent under-informed.

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, concise sentence that front-loads the key information: when to use, what it does, and for what purpose. No filler or redundant content.

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 tool is simple (one parameter, no output schema), and the description covers the main purpose and timing. However, it lacks specifics about what 'scoped customer profile details' includes, potential error conditions, and the absence of an output schema means the agent cannot anticipate the return structure.

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 description does not mention the only parameter, session_token, but the phrase 'after verification' implies the token is a verification artifact, adding some semantic context. However, with schema description coverage at 0%, the compensation is minimal and the parameter's purpose remains implicit.

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 action ('load'), resource ('scoped customer profile details from CRM'), and context ('for booking'), which distinguishes it from siblings like get_customer_availability or list_customer_addresses. The verb 'load' precisely implies a read operation.

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?

Provides an explicit precondition ('Use after verification') and a clear purpose ('for booking'), which guides when to call this tool. It does not name alternatives, but the context is specific enough to avoid confusion with other booking-related tools.

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