Gitopia MCP Server

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

With no annotations, description carries full burden and discloses key traits: 'Signs and broadcasts an on-chain transaction' (write operation), 'Returns the new proposal ID' (output format), and 'proposer is automatically set' (side effect). Minor gap on failure modes or transaction costs.

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?

Well-structured with front-loaded purpose statement, followed by behavioral details, parameter guidance, and cross-references. Every sentence provides distinct value with no redundancy.

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?

Complete for a transaction tool with no output schema: explains return value (proposal ID), transaction nature, and auto-set proposer. Only minor gaps regarding gas fees or error handling prevent a 5.

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?

Despite 100% schema coverage, adds critical semantic context: the XOR relationship between 'dao' and 'group_policy_address' ('Provide...OR'), required vs optional parameter grouping, and the implicit 'proposer' parameter behavior not visible in 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?

States specific action 'create a text governance proposal for DAO voting' with clear verb and resource. Distinguishes from siblings like dao_vote, dao_exec, and dao_list_proposals through explicit naming in 'See also' section.

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?

Provides explicit when-to-use trigger ('Use this when you need to create...'). Lists three specific sibling alternatives (dao_list_proposals, dao_vote, dao_exec) to guide correct tool selection.

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