get_dao

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

No annotations provided, but description covers return fields and requirements. Implicitly a read-only operation, but does not explicitly state non-destructive nature. Lacks details on auth or rate limits, but adequate for a simple query tool.

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-loaded with usage guidance. Every word is valuable, no fluff.

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 simple structure (one param, no output schema), the description fully covers what the tool does, what it returns, and prerequisites. No gaps.

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 covers 100% of params with description 'DAO name or address'. Description repeats this but adds no new semantics beyond the schema. Baseline score 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 clearly states the tool returns DAO details including group_id and group_policy_address, which are needed for governance tools. It distinguishes itself from siblings like create_dao and dao_list_members by specifying its specific use case.

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?

Explicitly states when to use (when needing DAO details with group_id and group_policy_address) and mentions that these fields are required for governance tools. Also provides 'see also' references to related tools.

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