List Moonvy project pages

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing pagination behavior (despite limit/maxApiPages parameters), potential recursion, API call volume, or response format. Agents have no sense of side effects or performance implications for a discovery tool that should be called first.

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 sentences, zero fluff. The core action is stated upfront, and the usage hint is concise. Every word earns its place.

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 tool meant to be called first, essential context is missing: no output schema, no notes on pagination or performance, no explanation of how to interpret results. Without annotations or richer description, an agent cannot anticipate the volume of data or how to proceed after calling it.

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 only 33% (url has a description; limit and maxApiPages do not). The tool description adds nothing about these parameters—no explanation of what limit or maxApiPages control or how they interact. With low coverage, the description should compensate but does not.

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 a specific verb ('List') with clear resource ('folders and design files') and scope ('below a Moonvy project or directory URL'). It also differentiates itself from siblings by positioning as the entry point. The instruction 'Call this first when only a project URL is known' reinforces its distinct role.

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 says to call this first when only a project URL is known, giving clear when-to-use guidance. However, it does not delineate when not to use it or point to alternatives for more specific operations, though the sibling names imply that. The guidance is still actionable and helpful.

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