gorelo_create_project

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered by structured data. The description contributes nothing beyond that — no mention of permission requirements, validation failures on missing client/group IDs, or side effects such as watcher/lead assignment rules.

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 single short sentence has zero waste and is front-loaded, but it errs toward under-specification rather than conciseness — it conveys no structure for a tool whose payload is a 13-field nested object.

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 create tool with a required nested body object and no output schema, the description should say what comes back and how required foreign keys are sourced. Neither is addressed; the description is effectively one restated name against a rich 100%-documented schema.

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%, and the nested body documents all 13 properties including backdating fields and the SharedWithContactIds constraint. The description adds no parameter meaning, so the baseline 3 is appropriate.

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 ("Creates a project"), so the agent knows the operation. However, it adds essentially nothing beyond the tool name gorelo_create_project, and does not distinguish it from siblings such as gorelo_update_project, gorelo_list_projects, or gorelo_create_project_section.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g. needing valid ClientId/GroupId/LocationId/TypeId values), and no mention of related lookup tools like gorelo_list_clients or gorelo_list_project_types that would supply those identifiers.

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