Query DRep State

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered elsewhere. The description adds nothing beyond this and does not describe filtering behavior when drep_key_hash is omitted (e.g., full listing vs error), but it does not contradict the annotations.

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 short, front-loaded with the purpose, and organized into Args and Returns sections. However, the Args section simply repeats the schema at 100% coverage, which is low-value padding rather than earning its place.

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 simple one-parameter read tool with full annotations and complete schema coverage, the description covers purpose and the filter. Without an output schema, it only says "Returns: DRep state information" without characterizing the return shape, and it does not address what happens when no filter is supplied.

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 100% and the single parameter's description is identical to the description's arg note, so no additional meaning is added beyond the schema. With zero required parameters and one fully documented optional parameter, 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 states a specific verb+resource ("Query DRep state") and expands the acronym, making the purpose clear. It does not differentiate from similarly-named siblings like cardano_query_gov_state or cardano_query_committee_state, leaving some ambiguity in a crowded governance-family namespace.

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?

There is no guidance on when to use this tool versus alternatives such as cardano_query_gov_state or cardano_query_committee_state. The only usage signal is the word "Optionally," which implies the filter is not required but offers no conditions for when to apply it.

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