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

Annotations already declare readOnlyHint=true and openWorldHint=false, indicating a safe, read-only reference. The description adds value by enumerating the five groups and mentioning the scoring rules and four-minute review method, going beyond the bare annotations to clarify the tool's content and scope.

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, well-structured sentence that leads with the core identity ('The eighteen-item pass-or-fail scorecard') and then efficiently adds specifics (groups, scoring rules, review method). No filler or redundancy.

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 zero-parameter read-only reference tool with no output schema, the description adequately conveys the tool's content: eighteen items, five groups, scoring rules, and review method. While it does not enumerate the actual rules or output format, it gives a clear sense of what the agent will receive, which is sufficient for a static reference.

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 are zero parameters, and the schema is empty with 100% coverage. The description correctly adds no parameter information since none exist, meeting the baseline expectation for a parameterless tool. No further elaboration is needed.

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 explicitly identifies the tool as the eighteen-item pass-or-fail scorecard for dealership sales calls, structured in five groups, and mentions scoring rules and a review method. It clearly distinguishes itself from siblings like score_call (which likely applies the scorecard) by positioning this as the reference definition.

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 does not provide explicit when-to-use guidance or name alternatives. Its nature as a reference tool implies usage when an agent needs the scoring criteria, but it does not explicitly say to use this instead of score_call or roleplay_card, leaving some inference required.

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