smart_git_push

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

The description adds useful context: security-focused push, credential detection, file filtering, and deployment metrics tracking. It also states that tests must be run by the AI, which is a notable behavioral requirement. However, it fails to disclose blocking behavior on security/test failures or the dangerous forceUnsafe and skipSecurity overrides, which are critical for safe use.

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 brief and front-loads the core purpose. The second sentence about tests is awkward and vague, but overall there is no waste.

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?

For a tool with 7 parameters, a nested object, and destructive overrides, the description is too sparse. It does not explain the dangerous forceUnsafe and skipSecurity flags, nor the conditions under which security blocks are applied. With no output schema and minimal behavioral detail, an agent cannot fully assess the tool's risks.

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% parameter description coverage, so the baseline is 3. The description adds no meaningful parameter semantics beyond the schema; the test-results instruction loosely maps to testResults but does not explain the nested structure or requirements.

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 identifies a specific operation: a security-focused git push with credential detection, file filtering, and deployment metrics tracking. It distinguishes itself from typical git push tools and the sibling set, though it does not explicitly name alternatives.

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 gives no explicit guidance on when to use this tool vs alternatives, nor any exclusions. The instruction 'Tests should be run by calling AI and results provided' implies a required workflow but does not help an agent decide between this and siblings like release_tracking or deployment_readiness.

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