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

Annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds useful content-level context by listing the groups, scoring rules, and four-minute review method. However, it does not disclose what actually happens when the tool is invoked, such as whether it returns a static reference or a formatted card.

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, front-loaded sentence with no filler; the key identifying phrase 'eighteen-item pass-or-fail scorecard' comes first. It is concise, though the trailing list of groups and methods is packed together and could be slightly clearer.

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, no-output-schema tool, the description conveys the main content and purpose, which is reasonably complete. Still, it never explicitly states that invoking the tool returns the scorecard or how the agent should use the returned information, and it lacks any mention of how this relates to the sibling scoring tools.

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, so the description has no parameter burden to carry; the baseline of 4 applies. No input-schema information is missing or in need of clarification.

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 identifies the resource as an eighteen-item pass-or-fail sales-call scorecard and enumerates its content (five groups, scoring rules, review method). It goes well beyond the bare title, so an agent can tell this is the reference scorecard rather than an action like score_call. However, it lacks an explicit verb such as 'returns' or 'provides', so it is not a full 5.

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 gives no guidance about when to use this tool versus alternatives like score_call, roleplay_card, or conversation_signals. It says the scorecard contains scoring rules, but it never states conditions such as 'when you need the scorecard criteria, use this; when scoring a call, use score_call.'

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