github_git_create_tree

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

No annotations are present, so the description must disclose behavior. It only states 'Create a tree' - a write operation - but omits side effects, permission requirements, idempotency, or return value. This is insufficient for safe selection and 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 extremely concise (3 words), but conciseness is not helpful when it omits critical information. It lacks structure or additional sentences that would improve usefulness.

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 complexity of creating a Git tree (requires repository, possibly base tree, and entries), the description is severely incomplete. There is no mention of the body's required structure, the response format, or any links to related operations. The tool cannot be used correctly without external knowledge.

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 input schema has 100% coverage but each parameter's description is just its name (e.g., 'owner' for owner). The 'body' parameter is described as 'Request body (JSON object)' with no details on required fields like tree entries or base_tree. The tool description adds no additional meaning beyond the schema.

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 'Create a tree' clearly indicates the action (create) and resource (tree), but it does not explain what a Git tree object represents or how it differs from other git create tools like create_blob or create_commit. It is minimally clear but lacks context to distinguish from siblings.

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, prerequisites, or alternatives. The agent receives no hints about required base trees or appropriate scenarios.

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