mesa_ducklake_init_project

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

No annotations are provided, so the description carries the full burden and does a solid job: it discloses the three concrete side effects (sub-collection creation, AVU write, catalog registration) and explicitly states the tool is idempotent and safe to re-run. It stops short of stating required permissions or what happens if the path does not exist.

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 filler, with the core action front-loaded and the operational caveat (idempotency) placed last. Every clause conveys a distinct fact.

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 single-parameter mutation tool with no annotations and no output schema, the description covers the essential behavior and idempotency. It could be more complete by stating permission requirements and the failure mode for an invalid or nonexistent path, but nothing critical for correct invocation is missing.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already explains that irods_path is the root collection carrying the AVU. The description restates the same concept in prose ('project root') without adding format, constraint, or default details beyond the schema, so the baseline 3 applies.

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 and resource ('Enroll an iRODS collection as a MESA project') and then enumerates the concrete artifacts created (the .mesa/ducklake sub-collection, the mesa.enabled=true AVU, the DuckLake catalog registration). It is unambiguous what the tool does, though it never contrasts itself with adjacent siblings like mesa_policy_enable or ds_make_directory, which also touch collections and metadata.

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?

Usage is implied by 'Enroll an iRODS collection as a MESA project' and the idempotency note tells the agent re-running is safe, but there is no explicit when-to-use framing, no prerequisites (e.g. that the collection must already exist), and no named alternative for related setup tasks. Adequate but leaves the routing decision to inference.

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