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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuinely new context by disclosing the return shape (clients/projects/shoot counts) even though no output schema exists. It does not mention ordering or pagination, but for a small folder tree that gap is minor.

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, both earning their place: the first establishes what comes back, the second establishes when and why to call it. The action-driving instruction is front-loaded after the resource description, with no filler.

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?

With no parameters, no output schema and rich annotations, the description carries the remaining burden well by describing the returned hierarchy. It stops short of telling the agent what identifiers the folders expose for use when filing new shoots, which is the one thing an agent would still need to infer.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. It correctly avoids inventing parameter semantics that don't exist.

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?

The description names the specific resource and its structure — 'the user's shoot folder tree — clients, projects and how many shoots sit in each' — so an agent knows this returns an organizational hierarchy with per-folder shoot counts, not a flat list. This clearly separates it from sibling mutators like create_shoot_project and create_video_shoot as well as from generic list_* tools.

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?

It gives an explicit call condition with a consequence: 'Call this before creating shoots so new work is filed next to what's already there instead of in a duplicate folder.' That is strong when-to-use guidance with a stated rationale, though it does not name the specific sibling tool (create_shoot_project) an agent should pair it with.

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