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 operation. The description adds no additional behavioral details beyond listing content areas, which is acceptable given the annotation coverage.

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, information-dense sentence that lists key content areas. It is front-loaded with the verb and resource, free of filler, and appropriately sized for its purpose.

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 tool has no parameters, an output schema, and annotations, the description adequately specifies what the tool describes (document kinds, resource classes, ratios, suppressions, citations). This is sufficient for an agent to invoke the tool correctly and understand its scope.

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 tool has zero parameters, so the schema is fully covered. Per the rubric, a tool with no parameters receives a baseline of 4, and the description does not need to explain parameter syntax. The content list helps the agent understand what will be described.

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 verb 'Describe' with a specific resource: 'MISO accreditation document kinds, resource classes, ratios, suppressions, and citations.' It explicitly names MISO, distinguishing it from sibling tools like describe_power_capacity_accreditation_pjm_v1 and describe_power_capacity_market_miso_v1.

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 context is clear: the tool should be used when one needs to understand MISO accreditation document kinds, resource classes, ratios, suppressions, and citations. It does not explicitly state exclusions or alternatives, but the domain is well-specified, and the tool name itself differentiates from PJM equivalents.

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