hyperd.governance.summarize

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

No annotations provided, but description adds valuable behavioral context: it is LLM-summarized and costs $0.10 USDC. This helps the agent understand side effects and resource consumption. However, it doesn't mention latency or error handling.

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-load the purpose and add critical details (cost, LLM usage, output structure). No wasted words.

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?

No output schema, but description adequately describes the return structure. Mentions cost and LLM usage. Could be improved by noting any limits on proposal size or response time, but sufficient for a simple tool.

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% for the single parameter, and the description in the schema already explains it. The tool description adds no new semantic detail about the parameter beyond 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?

Clearly states the tool summarizes DAO governance proposals from Snapshot or Tally URLs. Specifies structured output (impact analysis). Distinguishes itself from sibling tools by being governance-proposal specific.

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?

Description clearly states what the tool does but does not explicitly specify when to use it over alternatives or when not to use it. No guidance on prerequisites or exclusions.

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