git_exec

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

The description lacks detail on side effects, permissions, or safety. With no annotations, the agent gets no warnings about potential destructive operations from arbitrary git commands.

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 very short, which is concise but at the expense of necessary detail. It lacks structure and does not provide information beyond the bare minimum.

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 executes arbitrary git commands, the description is severely incomplete. It omits return values, valid commands, and behavioral traits, making it hard for an agent to use correctly.

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 has 0% description coverage for the 'args' parameter. The description adds no information about what arguments are expected, their format, or constraints, leaving the agent completely uninformed.

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 states 'Run a Logseq Git command,' which indicates it executes a git command within Logseq. However, it is vague about which commands or scope, and does not distinguish from sibling tools like git_load_ignore_file.

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 on when to use this tool versus alternatives like git_load_ignore_file or git_save_ignore_file. There is no mention of prerequisites or context for execution.

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