AgentFund MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that the tool generates transaction data (not executes it) and that a funder sends ETH, which adds useful context about the workflow. However, it lacks details on permissions, error handling, or what the generated data looks like, leaving gaps for a mutation-related 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?

The description is front-loaded with the core purpose in the first sentence, followed by role clarification and usage guidance. Every sentence earns its place by adding necessary context without redundancy, making it efficient and well-structured for quick understanding.

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's complexity (creating a fundraise with financial transactions), lack of annotations, and no output schema, the description is moderately complete. It covers the purpose, roles, and basic workflow but misses details on return values, error cases, or security considerations, which could be important for an agent invoking this 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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'milestones' and 'ETH' in context, but it doesn't provide additional syntax, format, or usage details for the parameters. This meets the baseline for high schema coverage.

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 specific action ('Generate transaction data for creating a new AgentFund fundraise'), identifies the resource (AgentFund fundraise), and distinguishes it from siblings by focusing on proposal creation rather than checking milestones, finding projects, generating release requests, getting projects, or getting stats. It explicitly mentions 'when you want to propose a project for funding,' which sets it apart from other tools.

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 description provides explicit guidance on when to use this tool ('Use this when you want to propose a project for funding') and clarifies the roles involved ('YOU provide your agent address... A FUNDER will execute this transaction'), which helps differentiate it from alternatives like checking milestones or finding projects. It implicitly excludes usage for other actions by focusing on initial proposal creation.

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