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

Annotations already indicate readOnlyHint=true and openWorldHint=true, and the description adds meaningful behavioral detail by specifying the output format: pass/fail/not observable per item, including evidence and a coaching note. This goes beyond the annotations by clarifying what the tool returns, though it does not discuss auth, rate limits, or error handling.

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, focused sentence that front-loads the core action and immediately specifies the scoring criteria and output. There is no filler or redundancy, but it is slightly long and could be split into two sentences for readability without loss of meaning.

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?

With one simple parameter and no output schema, the description covers the input and the main output categories, but it does not specify the exact return structure (e.g., JSON shape, per-item format, whether coaching note is a single string or per-item). Additional detail about the response format would make it more complete for an agent.

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 100% and the only parameter 'transcript' is clearly described in the schema as 'Transcript, notes or a summary of one call, up to 6,000 characters.' The tool description repeats this concept but does not add new meaning beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb ('Scores'), a clear resource ('dealership sales call transcript, notes or summary'), and a specific scoring framework ('eighteen-item BDC scorecard'). It also outlines the output per item (pass/fail/not observable with evidence and coaching note), which fully distinguishes it from siblings like score_crm_note.

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 implies usage by describing what the tool does, but it does not explicitly state when to use it versus alternatives such as score_crm_note or call_scorecard. There is no when-not guidance or explicit routing to sibling tools, leaving the agent to infer the appropriate context.

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