ds_create_ticket

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

No annotations are provided, so the description carries the full load; it does add real behavioral context by disclosing the return content (ticket string plus applied restrictions) and an authorization constraint (anonymous users may not create tickets). It stops short of describing persistence/lifecycle implications of creating a ticket or any rate limits.

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 short sentences, front-loaded with the core action and followed by the return value and precondition. No filler or restatement of the title.

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 seven-parameter creation tool with no output schema, the description covers purpose, return content, and one key precondition, and the schema fully documents parameters. It could go slightly further on permission requirements or ticket lifecycle, but nothing essential to a correct call 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?

Schema description coverage is 100% with all seven parameters documented (mode enum, expiry, uses_allowed, host/user restrictions, write_byte_limit), so the schema already does the heavy lifting. The description only echoes the read/write mode distinction and adds no syntax or interaction guidance beyond the 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 a specific verb (create) and resource (iRODS ticket) plus scope (data object or collection) and the access-mode dimension. It is clearly distinguishable from siblings like ds_modify_ticket and ds_delete_ticket by its creation semantics, though it never names those siblings.

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 the name and the 'read or write' framing, and one precondition is given ('Anonymous users may not create tickets'). However there is no explicit guidance on when to use this versus ds_modify_ticket or ds_use_ticket, and no note on required permissions for non-anonymous users.

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