fabric_git_commit

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

With empty annotations, the description must disclose behavioral details but only hints at modes. It does not explain whether the operation is destructive, what happens to uncommitted changes, or if a commit is created. The description lacks transparency about side effects and requirements.

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 efficient sentence with no unnecessary words. It is appropriately front-loaded with the core purpose. However, it could be slightly expanded to include key behavioral notes without becoming verbose.

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 five parameters, no output schema, and lack of annotations, the description is too sparse. It does not mention return values, error conditions, or the need for an existing Git connection. The agent lacks essential context to use the tool 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 coverage is low (40%), but the description adds negligible meaning beyond the schema. It mentions modes matching the enum but does not clarify parameters like comment, workspaceHead, workspace, or items (beyond the schema's own description). The description fails to compensate for the low 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 verb 'commit' and resource 'workspace changes to Git', specifying the two modes 'All or Selective'. It is distinct from sibling git operations like connect or get status. However, it could be more precise by mentioning that it commits items or changes to items.

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 alternatives like fabric_git_update_from_git or fabric_git_initialize. There is no mention of prerequisites (e.g., an existing Git connection) or scenarios where this tool is appropriate, leaving the agent without adequate decision support.

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