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

Annotations already indicate write activity (readOnlyHint=false) and non-destructiveness (destructiveHint=false), but the description adds no additional behavioral disclosure—such as uniqueness requirements, overwrite behavior, or success/failure conditions. It simply states the action without further explanation.

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 one short sentence, front-loaded and efficient with zero waste. While it may be too terse for a complex tool, for a straightforward create operation it is appropriately sized, though a bit more detail could have been included without sacrificing conciseness.

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 a nested request body with required fields, but the description only says 'Create a scoring profile.' It doesn't explain what a scoring profile is, what the profileType affects, or what the expected outcome is. There is no output schema, so the description carries the burden of explaining the effect, which it fails to do.

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 description coverage is 100%, with the profileType parameter having an explicit description ('Object type this profile will score') and the name parameter having an example. The tool description adds no parameter-level detail, but the schema adequately informs the agent, so the baseline of 3 is appropriate.

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 action ('Create') and the resource ('a scoring profile'), distinguishing it from sibling tools like scoring-profile-update or scoring-profile-delete. However, it lacks any additional context about what a scoring profile entails, so it's clear but not fully descriptive.

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, no prerequisites, and no mention of related tools such as scoring-profile-update or scoring-assignment-create. It's a bare statement with no usage context.

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