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

The description adds no behavioral context beyond what the annotations already declare (readOnly, openWorld, idempotent, not destructive). It does not mention potential errors, rate limits, authentication requirements, or whether the lookup is exact or partial. With annotations present, the bar is lower, but the description still contributes nothing.

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 extremely concise, consisting of a short phrase with no fluff. It is front-loaded with the key information. However, it is a noun phrase rather than a complete sentence, which could be structurally improved by adding an explicit verb.

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?

Given the tool's simplicity (1 param, no output schema), the description is not complete enough. It does not describe the return format or what 'scores' means, nor does it differentiate from connect_scores_by_account or connect_scores_batch. An agent might wonder if this returns a single score or a list, and whether it requires authentication.

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 coverage is 0%, so the description must compensate. It adds the qualifier 'public' to 'username,' clarifying that the parameter refers to a Connect public username. However, it does not specify format, case sensitivity, or any constraints beyond what the schema's minLength:1 provides. For a single parameter, this is adequate but not thorough.

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 states a clear resource ('Scores') and identifier ('Connect public username'), which aligns with the tool name. It does not explicitly use a verb like 'get' or 'retrieve,' but the intent is unambiguous. It does not contrast with siblings like connect_scores_by_account or connect_scores_batch, but the 'public username' qualifier provides some distinction.

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. It does not mention connect_scores_by_account or connect_scores_batch, nor does it explain scenarios where a public username is appropriate versus other identifiers. An agent is left to infer usage from the name alone.

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