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

With no annotations, the description carries the burden of disclosing behavior. It mentions optional filtering and filter dimensions, but does not reveal potential pagination behavior, whether drafts are included, or what fields the returned scorecards contain. It sufficiently indicates a read-only operation, but lacks deeper behavioral insight.

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 only two sentences, front-loaded with the primary action. Every sentence contributes: the first defines the operation and scope, the second explains the purpose and filter options. There is no fluff or redundancy.

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 no output schema, so the description should provide context about return values. It mentions 'scorecard configurations' but does not specify response format, pagination behavior, or how drafts are handled. Combined with the lack of annotations, this leaves gaps for a complete understanding, though the core purpose is clear.

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 high (86%), so the schema already documents most parameteters. The description adds value by naming the filter dimensions (groups, entities, teams), but does not elaborate on nuances like the instruction to use only one identifier type or the meaning of pagination defaults. Thus it neither compensates for gaps nor significantly extends the schema.

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 opens with 'List all scorecards in the organization with optional filtering,' establishing a clear verb ('list') and resource ('scorecards'). It differentiates from siblings like 'getScorecard' (singular) and 'listScorecardScores' (scores) by focusing on the scorecards themselves.

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 clear context for when to use the tool: 'to understand quality standards, compliance requirements, and maturity models' and 'to find relevant scorecards.' It does not explicitly name alternatives or exclusions, but the intended use case is evident, especially compared to sibling tools that retrieve specific entities or scores.

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