git_command

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states the read-only, safe nature, which is a key behavioral trait, but it does not disclose what happens if an unsafe command is attempted, error behavior, or output format. This is adequate but not rich.

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 sentence that immediately conveys the tool's purpose and key restriction. Every word is purposeful, with no redundancy or filler, making it highly efficient.

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?

The tool is relatively simple (two string params, no output schema), and the description communicates the core read-only constraint. However, it omits any mention of return values, command whitelist specifics, or error handling, which would be useful given the lack of annotations. It is minimally complete but could be more thorough.

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 fully documents both parameters with descriptions and examples (e.g., 'log -10', 'diff HEAD~1'). The description adds no extra semantic detail beyond reasserting read-only constraints, so it does not compensate beyond the schema's 100% 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 clearly states the tool's function: 'Execute a read-only git command on a ShadowGit repository.' This specifies a concrete action (execute) and resource (git command on a repository), and the read-only distinction sets it apart from siblings like list_repos or session management 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?

The description notes that only 'safe, read-only commands are allowed,' implying it should be used for non-mutating operations. However, it does not explicitly provide when-to-use guidance or contrast with alternative tools, leaving the usage context somewhat implicit.

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