connect_scores_batch

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does reveal a filtering behavior (excludes users below minScore) and implies a read operation, but it does not state whether the operation is read-only, how it handles invalid or missing users, or any authentication or rate-limiting considerations. This is a significant gap for an unannotated tool.

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 sentence that front-loads the primary action ('Batch scores') and then tacks on the filter behavior. It is concise, with no redundant wording, and every part contributes to understanding the tool's purpose.

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 no output schema and no annotations, so the description must convey return format, safety, and usage context. It states only 'scores' without detailing the response structure, what happens when some users are not found, or whether the tool is read-only. This is insufficient for an agent to confidently invoke the tool correctly.

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 adds meaning to the filter parameter by explaining its purpose ('excludes users below minScore'), which is not described in the schema. However, it does not elaborate on the users parameter, which relies on the schema's 'Users to fetch scores for' description. With only 50% schema coverage, the description partially compensates but leaves key structural details (e.g., type field semantics) unexplained.

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 batches scores for linked accounts or Connect usernames, providing a specific verb and resource. It does not explicitly differentiate from sibling tools connect_scores_by_account or connect_scores_by_username, though the word 'batch' implies a multi-user scenario, creating some ambiguity.

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 offers no guidance on when to use this tool versus the single-account sibling tools. It does not mention conditions like 'use when you have multiple users' or exclusions for single lookups, leaving the agent to infer the intended context from the tool name alone.

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