connect_scores_by_username

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

With no annotations, the description carries the full behavioral disclosure burden. It only states the basic purpose and does not mention whether the operation is read-only, what response format to expect, pagination, rate limits, or error handling. This is a significant gap for a tool with no structured behavioral metadata.

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 short phrase with no redundant words, effectively front-loading the core resource. It is concise, but its brevity borders on under-specification, eliding useful context an agent could rely on.

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 simple one-parameter tool with no output schema, the description covers the basic function but lacks usage constraints, return value expectations, failure conditions, and alternative routing. An agent has no information about what 'scores' means in the response or how to handle errors, leaving significant 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?

The schema has one parameter 'username' (string, minLength 1) with 0% description coverage. The description adds the qualifier 'Connect public', which clarifies the username type and distinguishes it from internal or account identifiers. However, it does not explain the expected format, case sensitivity, or relationship to other identifiers, so compensation is partial.

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 'Scores by Connect public username' states the resource (scores) and the key input (username), but omits an explicit verb like 'list' or 'retrieve'. It is distinguishable from sibling tools such as connect_scores_by_account through the 'username' qualifier, though it does not explicitly differentiate. It is clear and resource-focused, but not as specific as it could be.

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 provides no guidance on when to use this tool versus alternatives like connect_scores_batch or connect_scores_by_account. There is no mention of conditions, exclusions, or scenario-based routing, leaving the agent to infer usage purely from the tool name.

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