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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral detail about the optional filter excluding users below minScore, but it does not disclose behavior for invalid users, missing scores, batch size limits, or the response shape.

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 one concise, front-loaded sentence. It states the primary purpose first and then provides the optional filter behavior with concrete score ranges. No filler or redundant restatement of the schema is present.

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 has a nested users array and no output schema, so the description should clarify how to specify linked accounts versus usernames and what the caller can expect in return. It covers the filter well, but the user-identification ambiguity and lack of any response/error context leave meaningful gaps.

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 50%, so the description partially compensates by adding the minScore ranges and clarifying that the filter excludes low-scoring users. However, it does not explain the users parameter semantics—specifically how to distinguish linked accounts by id versus Connect usernames via the type and username fields—which is important given the nested schema.

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 uses a specific verb ('Batch scores') and identifies the resource ('linked accounts or Connect usernames'), making the core purpose clear. It does not explicitly contrast with the sibling tools connect_scores_by_account and connect_scores_by_username, but the word 'batch' plus the combined scope helps differentiate it.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The word 'Batch' implies use for multiple users, but the description never mentions alternatives like connect_scores_by_account or connect_scores_by_username or states when a single lookup would be more appropriate.

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