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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered structurally. The description adds useful scoping context (it exposes the markdown tree with issues/, sprints/, views/), but says nothing about what happens with an invalid or missing path, whether output is flat or nested, or ordering.

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 short sentences with the key fact front-loaded; the second sentence earns its place by naming the tree contents. Minor waste from restating the title verbatim in the first sentence.

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 output schema and one undocumented parameter, the description should explain path semantics and the shape of the returned listing, and it does neither. An agent can guess at a root listing but cannot reliably navigate to issues/ or sprints/ from this text.

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 only 50% – project_key is documented in the schema, but path has no description and only a default of empty string. The description does not clarify whether path is relative to project root, whether it needs a trailing slash, how to address the named subdirectories, or that an empty path means root, so it fails to compensate for the coverage gap.

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?

Specific verb plus resource ('List a directory of the project tree') with a follow-up sentence naming the md tree and its top-level entries. It's clear what the tool does, but it doesn't distinguish itself from adjacent siblings like read_file, list_docs, or get_doc, which an agent could plausibly pick instead.

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 when-to-use guidance, no mention of when to prefer read_file or get_doc, and no prerequisites. The second sentence gives content examples but not selection criteria, so the agent must infer routing from the name alone.

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