Create project

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

Annotations already declare non-read-only, non-destructive, non-idempotent, non-open-world, so the safety profile is covered. The description goes beyond them by disclosing real side effects: the caller is granted admin, the project is returned, and it carries no grants to org models, machines, skills, or secrets — which tells the agent follow-up grant calls are needed. It does not flag duplicate-name behavior despite idempotentHint=false.

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, front-loaded with the action and return, followed by the one piece of non-obvious state (empty grants). Every clause carries information and nothing is padded.

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 two-parameter create tool with no output schema, the description covers the action, the caller's resulting role, the returned object, and the initial grant state. It leaves out uniqueness constraints on name and error behavior, which are minor for a tool this simple.

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 both parameters (name, orgID) are well documented in the schema, including normalization and pattern constraints. The description adds no parameter-level detail, 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 ("Creates a project") and adds the two most important outcomes: the caller becomes admin and the project starts with no grants. It does not explicitly contrast with the only related sibling (projects_list), but the create/list distinction is unambiguous from the verb.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives or prerequisites beyond the implicit orgID requirement. An agent learns what the tool does but nothing about when it is the right call versus, say, grant_machines_add or other setup steps.

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