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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, the description does not disclose potential side effects, required permissions, error behavior, or rate limits. It only lists content categories and gives a use case, offering limited transparency about the tool's actual execution behavior.

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 concise, consisting of just two sentences. The first sentence front-loads the purpose and lists specific content areas, while the second adds a clear use case. Every word earns its place, 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?

Given the absence of an output schema, the description provides a useful overview of the returned content (configuration, rules, levels, weights, exemption settings, evaluation criteria). It does not describe the exact structure or error handling, but for a getter tool with a straightforward purpose, it offers enough context to set expectations. The usage context further aids completeness.

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 has 100% coverage for both parameters (tag and context) with clear descriptions. The tool description does not add any additional meaning about parameters, so it aligns with the baseline score of 3. It neither reinforces nor contradicts 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 uses a specific verb ('Get') and clearly identifies the resource ('scorecard') and the scope of details returned (configuration, rules, levels, weights, exemption settings, evaluation criteria). This distinguishes it from sibling tools like listScorecards and listScorecardScores, which focus on listing rather than complete detail retrieval.

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 this tool ('understanding how services are evaluated and what standards they must meet'), implying it is the right choice when a comprehensive view of a scorecard is needed. It does not explicitly mention alternatives or exclusions, but the resource-specific wording helps differentiate it from sibling tools.

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