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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds no extra behavioral context such as pagination, ordering, or return format, but it does not contradict the annotations. Since the annotations handle the main concerns, a neutral score is appropriate.

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, 'List scoring profiles', with no redundant words. It is concise and front-loaded, immediately stating the core purpose without any fluff.

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 simplicity (0 params, no output schema, strong annotations), the description is minimally viable but lacks any note about what is returned or if there are any limits. It does not address pagination or whether it returns all profiles system-wide or only owned ones, which could lead to ambiguity in broader use cases.

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 there is no schema information to supplement. The baseline for 0 params is 4, and the description correctly avoids inventing parameter details. No additional parameter explanation is needed.

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 the specific verb 'list' with the resource 'scoring profiles', clearly indicating a read operation that returns multiple profiles. It distinguishes from siblings like scoring-profile-get or scoring-profile-create by the action word, though it does not specify scope or filter criteria.

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 guidance is provided on when to use this tool versus the many sibling tools (e.g., scoring-profile-get for a single profile, or scoring-rule-list for rules). There is no mention of prerequisites, alternatives, or exclusions, leaving the agent to infer context 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.