create_collective

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true. The description adds genuine value by disclosing that creating a Collective also creates a Nextcloud Team, which is behavioral context beyond the annotations. However, it does not disclose failure modes, name-conflict behavior, or what happens on duplicate names. No contradiction with annotations.

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 with no filler, front-loading the core purpose before the side effect and the optional parameter. Efficient and scannable; nothing extraneous.

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 2-parameter create tool with annotations covering the mutation profile, the description covers the purpose and the important Team-creation side effect. No output schema exists and the description doesn't describe the return value, but that is a minor gap for a create operation. Reasonably complete.

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 coverage is 100% — both name and emoji are documented in the schema, including that name becomes the folder name in Files. The description merely echoes the emoji parameter ('Optionally set an emoji icon') without adding anything beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 (Collective), and adds the meaningful side-effect that the underlying Nextcloud Team is also created. The 'create' verb clearly differentiates it from siblings like update_collective, list_collectives, and delete_collective. Unambiguous and specific.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is implied by the verb and tool name rather than stated. The side-effect note about creating a Nextcloud Team provides some decision-relevant context, but nothing routes the agent away from the closely related update_collective or delete_collective.

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