AgentFund MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes what information is returned but doesn't address important behavioral aspects: whether this is a read-only operation, if it requires specific permissions, potential rate limits, error conditions, or data freshness. The description is purely functional without operational context that would help an agent use it safely and effectively.

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 efficiently structured in two sentences that directly communicate the tool's function and output. The first sentence states the core purpose, and the second elaborates on specific data returned. There's no wasted text or redundancy. However, it could be slightly more front-loaded by incorporating the output details into the initial statement.

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 read operation with one parameter and no output schema, the description provides adequate functional information about what the tool does and what data it returns. However, without annotations and with sibling tools that might overlap in functionality, it lacks sufficient context about operational constraints, differentiation from alternatives, and error handling. The description is minimally complete but leaves gaps in practical usage guidance.

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 fully documents the single 'projectId' parameter. The description doesn't add any parameter-specific information beyond what's in the schema (no format examples, validation rules, or relationship to other tools). This meets the baseline expectation when schema coverage is complete.

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's purpose: 'Check the current milestone status of a project' with specific details about what information is provided (milestone position, released amount, remaining amount). It distinguishes itself from siblings like 'agentfund_get_project' by focusing specifically on milestone tracking rather than general project information. However, it doesn't explicitly contrast with all siblings like 'agentfund_generate_release_request' which might be related to milestone releases.

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 no guidance on when to use this tool versus alternatives. While it implies usage for checking milestone status, it doesn't specify scenarios where this is preferable over 'agentfund_get_project' (which might include milestone data) or when to use 'agentfund_generate_release_request' instead. There's no mention of prerequisites, timing considerations, or explicit alternatives.

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