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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so safety is covered. The description adds real data-model behavior beyond that: modules are organization-level and shared across projects while test-case/test-run folders are project-scoped. It does not describe return shape or pagination, but no output schema exists to carry that either.

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 tightly written sentences with the core action front-loaded, followed by the type taxonomy and the parameter rule. No filler and nothing repeated that the schema already says at greater length.

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-param read tool with full schema coverage and safety annotations, the description supplies everything needed to choose the right tree and parameters. The only gap is return format/pagination, which is minor given there is no output schema to align with.

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%, so both parameters and the enum are already documented in the schema, making this the baseline case. The description restates the tree default and the tree/project_id coupling, which is mildly reinforcing but largely duplicative of the schema text.

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 the specific verb and resource ('Get a folder tree') and immediately enumerates the three folder types the Test Manager model contains, including which are per-project vs organization-level. An agent can distinguish this from tm_list_modules and tm_list_projects without opening a schema.

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?

Gives clear context: pass project_id for test-cases/test-runs, omit it for modules, and select via the tree parameter (default test-cases). It also routes creation work to tm_create_folder. It stops short of an explicit 'do not use this for X' exclusion, but coverage is strong.

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