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

With no annotations, the description carries the burden of conveying behavior. It transparently states that the tool 'Shows which rules need to be satisfied to reach the next maturity level,' making it clear this is a read-only informational query. It does not detail output format or edge cases, but the behavioral intent is unmistakable.

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?

Two concise sentences, front-loaded with the core action and easily scannable. Every word contributes to explaining either the tool's function or its value, with no redundancy or filler.

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 tool with 3 parameters, no output schema, and no annotations, the description adequately conveys what the tool returns (actionable next steps/rules) and its purpose. It could be slightly more explicit about the output structure or potential failure modes, but the current description is sufficient for an agent to know what to expect.

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%, so the baseline is 3. The description does not add additional parameter-level meaning beyond what the schema already provides, but it does reinforce the purpose of the entity and scorecard parameters by tying them to maturity-level progress.

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 a specific verb ('Get') and identifies the resource ('actionable next steps for an entity to improve its scorecard performance'). It clearly distinguishes this tool from siblings like getScorecard or listScorecardScores by focusing on improvement guidance rather than raw scores or definitions.

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 gives clear context for when to use the tool: when teams need to prioritize improvements and track compliance goals. It does not explicitly name alternative tools or exclusions, but the purpose is specific enough for an agent to decide when this tool is appropriate.

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