gitee_get_tree

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

With no annotations, the description must fully disclose behavioral traits, but it only states the basic function. It does not mention that the tool is read-only, what the response contains, or any limits (e.g., tree size), which is insufficient for safe invocation.

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?

The description is a single, brief sentence, making it very concise. It is front-loaded with the core action, but it may be overly minimal, lacking details that would fit within a concise structure.

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?

Given the tool's simplicity and lack of output schema, the description should at least explain what a git tree is and what data the response includes. It does not, leaving an incomplete picture for the agent.

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% (all 4 parameters have descriptions), so the description adds minimal value beyond the schema. It does not clarify the 'recursive' parameter's effect or format of 'sha', meeting the baseline for high coverage.

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 'Get a git tree by SHA' clearly specifies the action (get), resource (git tree), and how (by SHA). It distinguishes from sibling tools like gitee_get_blob and gitee_get_branch, but could be more explicit about what a git tree represents.

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 guidance is provided on when to use this tool versus other 'get' tools, such as gitee_get_blob or gitee_get_branch. There are no exclusions, prerequisites, or alternative suggestions, leaving the agent without contextual direction.

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