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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: instructions live in the UI and deletion is unavailable through this connection, which prevents an agent from assuming a full CRUD surface.

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?

Three short sentences, front-loaded with the core action, then two tightly-scoped caveats. No filler or restated 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 single-required-param create tool with annotations covering safety and no output schema, the essentials are present. A minor gap is that it doesn't hint at the result (e.g., whether a project ID is returned), which would matter for chaining into tm_create_folder or tm_create_test_case.

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?

With 100% schema description coverage and only three simple params (name, tags, description), the schema carries the parameter meaning. The description adds no format, constraint, or default details beyond it, 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 ("Create a new Test Manager project"), which clearly separates it from sibling creation tools like tm_create_folder or tm_create_test_case. It stops short of explicitly contrasting those siblings, but the resource scoping is unambiguous.

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?

The note that "Project & Org Instructions (Memory Layer) stay managed in the UI" implicitly tells the agent not to attempt that here, and the deletion note rules out one adjacent action. However, there is no explicit when-to-use guidance or routing to alternatives such as tm_update_project or tm_create_folder.

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