fabric_summarize_git_diff

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and purpose, without mentioning side effects, permissions, limitations, or how the summary is produced. This leaves the agent without critical safety or operational context.

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, compact sentence with no redundant information. It is front-loaded with the action and resource, making it easy to scan.

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 simple with one parameter, but the description provides no output schema and minimal behavioral detail. Given the many overlapping sibling tools (e.g., fabric_summarize, fabric_explain_code), the lack of usage exclusions leaves the description only partially complete.

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 schema's parameter description is generic ('The input text to process'), but the tool description clarifies that the input should be git diff output. This adds meaningful semantic context beyond the schema, which is especially valuable for a single-parameter tool.

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 'Summarize git diff output for code reviews' uses a specific verb ('summarize') with a clear resource ('git diff output') and an explicit purpose ('for code reviews'). This clearly distinguishes it from generic summarization tools like fabric_summarize and code-specific tools like fabric_explain_code.

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 phrase 'for code reviews' implies the tool is intended for code-review contexts, giving some usage guidance. However, it does not explicitly contrast with sibling tools such as fabric_summarize or fabric_explain_code, nor does it state when not to use it. The guidance is implied rather than explicit.

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