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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read. The description adds no behavioral context beyond the annotations, such as return format or potential errors. It does not contradict annotations.

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 sentence, 'Get a scoring profile', with no filler or redundant information. It is front-loaded and every word contributes to the basic purpose, though it may be too terse to convey deeper context.

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 read operation with comprehensive annotations, the description is minimally adequate. However, it does not mention what is returned (e.g., the full profile object), error cases, or relation to list/update operations, making it less complete than ideal in the absence of an output schema.

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 input schema fully describes the single parameter (profileId) with a description 'Scoring profile UUID' and format/pattern constraints, so schema coverage is 100%. The description adds no additional parameter meaning beyond what the schema provides, aligning with the baseline for high coverage.

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 'Get' with the resource 'a scoring profile', clearly indicating a fetch operation. However, it does not explicitly differentiate from sibling tools like scoring-profile-list, which also retrieves scoring profiles, relying on the singular vs. plural 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?

No guidance is provided about when to use this tool versus alternatives such as scoring-profile-list or scoring-profile-update. There is no mention of prerequisites, such as knowing the profile ID, or exclusions. The required profileId parameter implies usage but the description itself gives no context.

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